This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GIT: Monotonically increasing trunk and release branch ids

From: Joel Brobecker <brobecker at adacore dot com>
To: Joseph Myers <joseph at codesourcery dot com>
Cc: Jakub Jelinek <jakub at redhat dot com>, "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, Jonathan Wakely <jwakely at redhat dot com>, gcc at gcc dot gnu dot org
Date: Fri, 10 Jan 2020 22:11:40 +0400
Subject: Re: GIT: Monotonically increasing trunk and release branch ids
References: <20200110163852.GV10088@tucnak> <alpine.DEB.2.21.2001101655390.29813@digraph.polyomino.org.uk> <20200110171723.GW10088@tucnak> <alpine.DEB.2.21.2001101745130.29813@digraph.polyomino.org.uk>

> > > 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.

FWIW (with my GDB Release Manager hat, this time), some people have
asked about it shortly after GDB switched over to Git. I've been
signing them ever since.

-- 
Joel

References:
- GIT: Monotonically increasing trunk and release branch ids
  - From: Jakub Jelinek
- Re: GIT: Monotonically increasing trunk and release branch ids
  - From: Joseph Myers
- Re: GIT: Monotonically increasing trunk and release branch ids
  - From: Jakub Jelinek
- Re: GIT: Monotonically increasing trunk and release branch ids
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]