Hans Wennborg via llvm-dev
2018-Aug-01 16:20 UTC
[llvm-dev] [7.0.0 Release] The release branch is open; trunk is now 8.0.0
Hi everyone, The release branch for 7.0.0 was created off trunk at r338536 earlier today, and the trunk version was subsequently bumped to 8.0.0. Release blockers are tracked by https://llvm.org/PR38406 Please mark any bugs, old or new, that need to be fixed for the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be merged -- ideally by filing a blocker bug on https://llvm.org/PR38406, or by cc'ing me on the commit email. (Please try not to request merges over IRC, as they're easy to miss.) Please help with the release by notifying me about any bugs, commits, or other issues you think might be relevant. If it's not marked as blocking PR38406, or I'm not cc'd on an email about it, I'll probably miss it. What's next? In a day or two, once the branch appears reasonable stable, release candidate 1 will be tagged and testing of that can begin. Thanks, Hans
Martin J. O'Riordan via llvm-dev
2018-Aug-03 10:42 UTC
[llvm-dev] [7.0.0 Release] The release branch is open; trunk is now 8.0.0
Hi all, A few months ago I switched from using SVN for the LLVM project to using the GIT mono-repo, but I am still not particularly good at using GIT. How can I use the GIT command-line interface to select to the exact same set of sources used for the v7.0.0 branch, or for the sources at a particular SVN revision (e.g. r338536)? Is this even possible? Thanks, MartinO -----Original Message----- From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Hans Wennborg via llvm-dev Sent: 01 August 2018 17:21 To: Release-testers <release-testers at lists.llvm.org>; llvm-dev <llvm-dev at lists.llvm.org>; cfe-dev <cfe-dev at lists.llvm.org>; LLDB Dev <lldb-dev at lists.llvm.org>; openmp-dev (openmp-dev at lists.llvm.org) <openmp-dev at lists.llvm.org> Subject: [llvm-dev] [7.0.0 Release] The release branch is open; trunk is now 8.0.0 Hi everyone, The release branch for 7.0.0 was created off trunk at r338536 earlier today, and the trunk version was subsequently bumped to 8.0.0. Release blockers are tracked by https://llvm.org/PR38406 Please mark any bugs, old or new, that need to be fixed for the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be merged -- ideally by filing a blocker bug on https://llvm.org/PR38406, or by cc'ing me on the commit email. (Please try not to request merges over IRC, as they're easy to miss.) Please help with the release by notifying me about any bugs, commits, or other issues you think might be relevant. If it's not marked as blocking PR38406, or I'm not cc'd on an email about it, I'll probably miss it. What's next? In a day or two, once the branch appears reasonable stable, release candidate 1 will be tagged and testing of that can begin. Thanks, Hans _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
Tim Northover via llvm-dev
2018-Aug-03 11:07 UTC
[llvm-dev] [7.0.0 Release] The release branch is open; trunk is now 8.0.0
On Fri, 3 Aug 2018 at 11:42, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote:> A few months ago I switched from using SVN for the LLVM project to using the GIT mono-repo, but I am still not particularly good at using GIT. How can I use the GIT command-line interface to select to the exact same set of sources used for the v7.0.0 branch,Do you mean the commit that was forked to create the 7.0 branch, the commit that was released as 7.0.0, or the current status of the 7.0 branch? In turn they'd be: 1. git merge-base master origin/release_70 2. These are stored as tags I believe, though the format has changed and we only started recently. "git tag" lists what we have now, with an obvious mapping to releases (for a human). 3. Just plain origin/release_70> or for the sources at a particular SVN revision (e.g. r338536)?For now, svn revisions are stored in notes attached to each git commit. Annoyingly they're not downloaded by default so you have to run this once: $ git fetch origin refs/notes/*:refs/notes/* After that they'll come along with every "git fetch" or "git pull". Once you have those, I personally just grep a "git log" for a revision I'm interested in. You could package some variant of $ git log --grep "git-svn-rev: 338839" -1 into a script pretty easily though. Cheers. Tim.