This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GIT: Monotonically increasing trunk and release branch ids
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, Jonathan Wakely <jwakely at redhat dot com>, <gcc at gcc dot gnu dot org>, <brobecker at adacore dot com>
- Date: Fri, 10 Jan 2020 17:05:04 +0000
- Subject: Re: GIT: Monotonically increasing trunk and release branch ids
- Ironport-sdr: f+f9JMipx6N3j/3Naw5zNNKzkL+u4G8GAMnX85rcH8uvVlQTfLlWCTTkOwfoLXD6ooL2ldm0db pGe3lTP1BeNXr/rZvR6gGwVB9PIzLGJYXeGzBGBgKiJ6knToe+CIM9UAYH8s0FN6j4C99eWITA X8XWeT6y4Bs2eSLCuWf0q5CAMn0jogRGnxuBE1UoMHetu7y3KVbVNBO+6x5L6DmtCGFKHuebo6 w8rI/9bGgrV4cDUb85CkssZEr9c9Fk2+8bdyd0sziI2N9Sfi0itPvvwPhhFGYvjkfWfmvMZgQd hjc=
- Ironport-sdr: vyadnnUF+c+lUnalrt6jnZorPxSDhsKk6/23anboK66mNIU8qJUNqlXzXinAwumVgR5YsEfvSa PkqNvyikDwIwIYdK6rMLI1o/FuNWwbczEj8WMfv+aExXo9IIyy7TMHuR0bkTLpnYiELKLesjx3 GAxB28L9ZYkCiKtKtcxUUafcQRiQ/vLtlEo00abaLbu1u9aN775apUR+rovvlT+pGgVfeTyQsF siYIBoCHhI27/TLHWzQlCse4gEG91XTiAG6FUTz7MiTkbXi7hIlYWUiLire2fgcwYlwJpOpNS+ 8yA=
- References: <20200110163852.GV10088@tucnak>
On Fri, 10 Jan 2020, Jakub Jelinek wrote:
> We would need to add some tags (I wouldn't bother with pre-GCC 5 era,
> because that doesn't have single number version numbers in the branch
> names), like:
> for r in 10 9 8 7 6; do
> git tag branchpoints/gcc-$r `git rev-list $(git merge-base origin/master origin/releases/gcc-$(expr $r - 1))..origin/master | tail -1`
> done
> git tag branchpoints/gcc-5 `git rev-list $(git merge-base origin/master origin/releases/gcc-4.9)..origin/master | tail -1`
Those look like the start of GCC version N development (just after the
branchpoint for N-1), not the branchpoint as commonly understood; naming
them "branchpoints" seems confusing.
> I'm sorry for my limited git-fu, could those branchpoints
> tags be something that is fetched by default (given they would be added only
> once a year for each trunk commit after the branching, usually the
> BASE-VER bumping to N+1.0.0)?
Any tag in refs/tags is fetched by default.
I think the existing git hook configuration expects you to push only
annotated tags, not lightweight tags (so you'd need to use -a / -s / -u
when creating those tags).
> As it is short, could it be something we'd put as first thing in the gcc-cvs
> mail subjects (of course, only for trunk and release branch commits; like
> the current svn mails start with rNNNNNN - ), and somewhere before or after the hash
> in the body which also makes it into bugzilla?
This seems like another thing that would need new features in the hooks to
support configuring email subjects and contents like that.
--
Joseph S. Myers
joseph@codesourcery.com