Re: [lldb-dev] [llvm-dev] Updates on SVN to GitHub migration

[NAKAMURA Takumi via lldb-dev]

James and Tom,

One question. Would the monorepo be fixed and would it not be re-created
after the day?

I am deeply cosmetic-checking the repo. For now, I haven't found critical
issues, though.

Takumi

On Sat, Oct 20, 2018 at 9:47 AM Tom Stellard via llvm-dev <
llvm-...@lists.llvm.org> wrote:

> TLDR: Official monorepo repository will be published on
> Tuesday, Oct 23, 2018.  After this date, you should modify
> your workflows to use the monorepo ASAP.  Current workflows
> will be supported for at most 1 more year.
>
> Hi,
>
> We had 2 round-tables this week at the Developer Meeting to
> discuss the SVN to GitHub migration, and I wanted to update
> the rest of the community on what we discussed.
>
> The most important outcome from that meeting is that we
> now have a timeline for completing the transition which looks
> like this:
>
> Tues Oct 23, 2018:
>
> The latest monorepo prototype[1] will be moved over to the LLVM
> organization github project[2] and will begin mirroring the current
> SVN repository.  Commits will still be made to the SVN repository
> just as they are today.
>
> All community members should begin migrating their workflows that
> rely on SVN or the current git mirrors to use the new monorepo.
>
> For CI jobs or internal mirrors pulling from SVN or
> http://llvm.org/git/*.git you should modify them to pull from
> the new monorepo and also to deal with the new repository
> layout.
>
> For Developers, you should begin using the new monorepo
> for your development and using the provided scripts[3]
> to commit your code.  These scripts will allow to commit
> to SVN from the monorepo without using git-svn
>
>
>
>
>
>
> [1] https://github.com/llvm-git-prototype/llvm
> [2] https://github.com/llvm/
> [3]
> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
>
>
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc3 has been tagged

[NAKAMURA Takumi via lldb-dev]

FYI, CentOS6 RPMs are here;
https://github.com/llvm-project/llvm-project-20170507/releases/tag/RELEASE_700%2Frc3

On Mon, Sep 10, 2018 at 11:13 PM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> 7.0.0-rc3 was just tagged (from branch revision r341805).
>
> No further release candidates are currently planned, so this is a
> release candidate in the real sense: unless any serious issues
> surface, this is what the final release will look like.
>
> Please run the test script, share your results and upload binaries.
>
> Please also take a look at the release notes and other docs; small
> changes to those are still welcome.
>
> The sources and docs will show up at
> https://prereleases.llvm.org/7.0.0/#rc3 anytime now, and binaries will
> be posted when they're ready.
>
> Thanks everyone for your work on this release!
>
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

[NAKAMURA Takumi via lldb-dev]

Paul,

Are you using llvm-project-20170507.git ?

Regarding to release_70, I am updating it manually, due to each
repo.git/release_70 might not be up-to-date. In fact, openmp.git/release_70
isn't yet.

Sorry for the inconvenience. Please be patient.

On Fri, Aug 3, 2018 at 10:44 PM via llvm-dev 
wrote:

>
>
> > -Original Message-
> > From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf Of
> Hans
> > Wennborg
> > Sent: Friday, August 03, 2018 9:40 AM
> > To: Robinson, Paul
> > Cc: Release-testers; llvm-dev; openmp-dev (openmp-...@lists.llvm.org);
> > LLDB Dev
> > Subject: Re: [cfe-dev] [7.0.0 Release] rc1 has been tagged
> >
> > On Fri, Aug 3, 2018 at 3:38 PM,   wrote:
> > > Hi Hans,
> > >
> > > I was just trying to push a release note about DWARF v5 support. I did:
> > >   git checkout release_70 # in the monorepo
> > >   git commit 
> > >   git llvm push
> > > but that fails.  How do you want to do release notes?
> >
> > I'm not familiar with "git llvm", but I suspect it doesn't work for
> > release branches. Can you just svn commit it instead?
>
> "git llvm" is a script for tying together the monorepo with svn.
> I'll do an svn checkout of the release branch and do the note there.
> --paulr
>
> >
> > Thanks,
> > Hans
> >
> > >> -Original Message-
> > >> From: cfe-dev [mailto:cfe-dev-boun...@lists.llvm.org] On Behalf Of
> Hans
> > >> Wennborg via cfe-dev
> > >> Sent: Friday, August 03, 2018 7:38 AM
> > >> To: Release-testers
> > >> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB
> Dev
> > >> Subject: [cfe-dev] [7.0.0 Release] rc1 has been tagged
> > >>
> > >> Dear testers,
> > >>
> > >> 7.0.0-rc1 was just tagged (from the branch at r338847).
> > >>
> > >> It's early in the release process, but I'd like to find out what the
> > >> status is of the branch on our various platforms.
> > >>
> > >> Please run the test script, share the results, and upload binaries.
> > >>
> > >> Thanks,
> > >> Hans
> > >> ___
> > >> cfe-dev mailing list
> > >> cfe-...@lists.llvm.org
> > >> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

[NAKAMURA Takumi via lldb-dev]

FYI, unofficial CentOS6 RPMs are there.
https://github.com/llvm-project/llvm-project-20170507/releases/tag/release_600_rc2

On Thu, Feb 8, 2018 at 5:52 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear testers,
>
> There's been a lot of merges since rc1, and hopefully the tests are in
> a better state now.
>
> 6.0.0-rc2 was just tagged, after r324506.
>
> Please test, let me know how it goes, and upload binaries.
>
> Thanks,
> Hans
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [4.0 Release] Schedule and call for testers

[NAKAMURA Takumi via lldb-dev]

I hope you could branch and tag to projects atomically. Are you able?

On Tue, Dec 6, 2016 at 3:26 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org> wrote:

> Dear everyone,
>
> There's still plenty of time left, but I'd like to get the schedule
> set before folks start disappearing for the holidays.
>
> Note that this release will also switch us to the new versioning
> scheme where the major version is incremented for each major release
> (i.e., when the 4.0 branch is created, trunk will become 5.0).
>
> If you'd like to help providing binaries and testing for your
> favourite platform, please subscribe to the release-testers mailing
> list [1].
>
> I propose the following schedule for the 4.0 release:
>
> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>
> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>
> - 21 February: Final tag. Binaries and release announcement a few days
> later.
>
> Unless there are any objections, I'll post this on the web page soon.
>
> Cheers,
> Hans
>
>
>   [1] http://lists.llvm.org/mailman/listinfo/release-testers
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [llvm-dev] Sequential ID Git hook

[NAKAMURA Takumi via lldb-dev]

"git-describe -t" works also for lw tags.

2016年7月4日(月) 2:48 Jared Grubb via cfe-dev :

>
> El jun. 30, 2016, a las 19:31, Matthias Braun via cfe-dev <
> cfe-...@lists.llvm.org> escribió:
>
>
> On Jun 30, 2016, at 4:14 PM, Renato Golin via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
>
> On 30 Jun 2016 10:20 p.m., "Robinson, Paul" 
> wrote:
> > We've since stopped creating the tags, and gotten used to not having
> > them.  We do the 'rev-list --count' trick which mainly gets recorded as
> > one component of the version number, and it has been working for us.
>
> Does that work for sub modules inside the umbrella project?
>
> How can you trigger a hook in the umbrella project for commits inside the
> sub modules?
>
> First: This is purely about generating sequential revision numbers, it
> does not help setting up a server hook to update the submodule references
> in the meta repository. The point I am trying to make here is that we only
> need to solve the problem of updating the submodule references, and that
> generating sequential ID numbers as an alternative to git hashes is no
> problem.
>
> As far as I can see we need the following operations for sequential ID
> numbers and they are all easy enough to perform with git on the client side:
>
> 1. Produce revision number for current checkout (to use in tool --version
> output):
> You can put something like
>   > echo "#define VERSION $(git rev-list --count HEAD)" > version.h
> in your buildsystem
>
> 2. Convert git hash to revision number:
>   git rev-list --count $HASH
>
> 3. Convert revision number $NUM to git hash:
>   git rev-list HEAD | tail -n $NUM | head -n 1
>
>
> I just want to point out another alternative that I often use in my
> projects:  (Example from buildbot repo I had handy)
>
> $ git describe
> v0.9.0b8-579-ge06cac6
>
> The format is "TAG-N-gREV", where TAG is the closest reachable git tag in
> the past ("v0.9.0b8"), N is the relative number of revisions past that tag
> (579), and REV is the short revision to make it unique and easy to locate
> ("e06cac6", the 'g' is a literal character that prefixes the revision). In
> other words, that "-579-" represents a monotonically increasing value
> relative to the named tag and might serve your purposes.
>
> Jared
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] Git Move: GitHub+modules proposal

[NAKAMURA Takumi via lldb-dev]

It has also submodules.
https://github.com/llvm-project/llvm-project-submodule

Both llvm-project(-tree) and (-submodule) have refs/notes/commits.

On Tue, Jun 28, 2016 at 1:13 AM Renato Golin via llvm-dev <
llvm-...@lists.llvm.org> wrote:

> On 27 June 2016 at 17:03, Rafael Espíndola 
> wrote:
> > I think that trying to create a ordering/rev number between independent
> git
> > repositories is fundamentally unreliable.
> >
> > If we want to keep llvm and clang in lock step we should probably
> probably
> > just have them in the same repository like
> > https://github.com/llvm-project/llvm-project.
>
> That is similar to the proposal we have, except that llvm-projects
> will have sub-modules.
>
> Having all of them in the same physical repository is a big problems
> for those that only use a small subset of the components, which is the
> vast majority of users, most of the time (all buildbots, Jenkins,
> local development, downstream users, even releases don't clone all
> repos).
>
> cheers,
> --renato
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] GitHub anyone?

[NAKAMURA Takumi via lldb-dev]

TL;DR :-)

Git-submodules works fine for bisecting for read-only use. I have the repo
to do that.
https://github.com/llvm-project/llvm-project-submodule

With a simple hooks/post-checkout, It should help effective bisecting.
https://github.com/chapuni/llvm-project-scripts/blob/master/hooks/post-checkout

It has refs/notes/commits, aka git-notes.

That said, I am afraid that submodules would lead us to the hell for
committers.
More discussions would be required to manage multiple git repos.

FYI, I have been using the unified repo,
https://github.com/llvm-project/llvm-project , for years.
It requires a wrapper script to invoke git-svn commit-diff.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

[NAKAMURA Takumi via lldb-dev]

I am ready, regarding to, http://bb.pgr.jp/

On Wed, May 25, 2016 at 5:54 AM Chris Bieneman  wrote:

> Meant to send this yesterday, but I want to remind everyone that we’re
> going to be raising the CMake minimum version to 3.4.3 next week.
>
> If you maintain bots please ensure that your bots are updated by end of
> day 5/29 so that we can move on 5/30 (next Monday).
>
> I have already heard from most bot owners either saying they had made the
> change, or scheduled to make it.
>
> If you have any questions or concerns please let me know.
>
> Thank you,
> -Chris
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev