This is the mail archive of the
mailing list for the GCC project.
Re: GIT: Monotonically increasing trunk and release branch ids
- From: Jason Merrill <jason at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Jonathan Wakely <jwakely at redhat dot com>, gcc Mailing List <gcc at gcc dot gnu dot org>
- Date: Sat, 11 Jan 2020 09:15:11 -0500
- Subject: Re: GIT: Monotonically increasing trunk and release branch ids
- References: <20200110163852.GV10088@tucnak> <CADzB+2=U=WBqu7uc37UrW_YOt45eOKEKhz=Fdg9vwUN1NGY8kQ@mail.gmail.com> <20200110214747.GD10088@tucnak> <20200111112801.GF10088@tucnak>
On Sat, Jan 11, 2020 at 6:28 AM Jakub Jelinek <email@example.com> wrote:
> On Fri, Jan 10, 2020 at 10:47:47PM +0100, Jakub Jelinek wrote:
> > Ah, you suggested g: rather than just g.
> > We could then support
> > rNNNNN (1-6 decimal digits) - the svn revs, either for old repo, or
> > g:XXXXX (X is any [0-9a-zA-Z_-], something else?, 1 or more chars) -
> gitweb with XXXXX
I was thinking that anything at all after g: should go to gitweb.
> > rNN-MMMMM (1-2 decimal digits, 1-6 decimal digits) - git undescr to hash
> > rNN-MMMMM-gXXXXX (perhaps limit X to hashes here, i.e. 7-40 hex digits)
> - gitweb with XXXXX
Why complicate this with the added 'g'?