This is the mail archive of the
mailing list for the GCC project.
Re: GIT: Monotonically increasing trunk and release branch ids
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Joseph Myers <joseph at codesourcery 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 19:11:49 +0100
- Subject: Re: GIT: Monotonically increasing trunk and release branch ids
- References: <20200110163852.GV10088@tucnak> <alpine.DEB.firstname.lastname@example.org> <20200110171723.GW10088@tucnak> <alpine.DEB.email@example.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Jan 10, 2020 at 05:47:16PM +0000, Joseph Myers wrote:
> > Ok, so what about basepoints instead?
> That seems a better name to me.
> > > 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).
> > Ok, would use -a then; or do we plan to GPG sign some tags such as releases?
> I think signing future release tags is probably appropriate.
> > > This seems like another thing that would need new features in the hooks to
> > > support configuring email subjects and contents like that.
> > Are the git hooks we use shared with AdaCore or GDB or where they come from
> > and can't be customized?
> Right now we have our own fork of the hooks in ~gccadmin/git-hooks. I
> hope that appropriately generic versions of the GCC-specific features can
> be developed that mean we can stop using our own fork at some point and
> symlink to the version used by GDB instead.
Ok, could that stuff be customized based on branch and repository names, or
some knob in a configuration file?
I'll have a look at the hooks.