> So, the current SVN mails are like:
> Subject: r280117 - in /trunk/libstdc++-v3: ChangeLog tes...
> To: gcc-...@gcc.gnu.org
>
> Author: redi
> Date: Fri Jan 10 15:27:50 2020
> New Revision: 280117
>
> URL: https://gcc.gnu.org/viewcvs?rev=280117&root=gcc&view=rev
> Log:
> libstdc++: Fix testcase f
On Sat, Jan 11, 2020 at 11:03:02AM +0100, Jakub Jelinek wrote:
> Here it is in patch form (against Joseph's git-hooks copy), but untested
> (both because the repo isn't converted yet, basepoints don't exist there
> either and because not sure how exactly it can be tested in a dry-run, say
> sending
Le 11/01/2020 à 14:49, Jakub Jelinek a écrit :
On Sat, Jan 11, 2020 at 07:43:17AM -0600, Segher Boessenkool wrote:
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
redirect to https://gcc.gnu.org/git/gitweb.cg
On Jan 11 2020, Jakub Jelinek wrote:
> g:releases/gcc-9@{yesterday} references (and, there we at least shouldn't
@{yesterday} operates on reflogs, a local concept that is useless
outside your own repository.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5
On Sat, Jan 11, 2020 at 12:28:01PM +0100, Jakub Jelinek wrote:
> For the redirectors, it could be something like following patch, except the
> last new redirect would need also a yet to be written cgi script that would
> git undescr the argument and print
> Location: https://gcc.gnu.org/git/gitweb.
On Sat, Jan 11, 2020 at 09:15:11AM -0500, Jason Merrill 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
> > > rN (1-6 decimal digits) - the svn revs, either for old repo, or
> > transformed
> >
On Sat, Jan 11, 2020 at 6:28 AM Jakub Jelinek 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
> > rN (1-6 decimal digits) - the svn revs, either for old repo, or
> transformed
> > g:X (X is any
On Sat, Jan 11, 2020 at 07:43:17AM -0600, Segher Boessenkool wrote:
> On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
> > Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
> > redirect to https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=NNN
> > and then just p
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
> Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
> redirect to https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=NNN
> and then just put as URL those
> https://gcc.gnu.org/g3b2b821c3f1bac2ac6dd2481f461ec33a13ea
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
> rN (1-6 decimal digits) - the svn revs, either for old repo, or
> transformed
> g:X (X is any [0-9a-zA-Z_-], something else?, 1 or more chars) - gitweb
> wit
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
> The changes I was asking for is, for gcc master and releases/gcc-* branch
> commits to have the monotonically increasing short ids (printed by git descr
> with the git aliases I've posted) both somewhere early
> in the subject before
On Fri, 10 Jan 2020, Jakub Jelinek wrote:
> We'll need to tweak maintainer-scripts/gcc_release in any case.
I now have a conversion of gcc_release to use git. Once the repository
conversion is done I'll test it for snapshot creation (which can be done
while the converted repository is still re
On Fri, Jan 10, 2020 at 02:15:30PM -0500, Jason Merrill wrote:
> Yep, this is a lot like I was suggesting at
>
>https://gcc.gnu.org/ml/gcc-patches/2019-08/msg01015.html
>
> except I didn't think it was necessary to trim the trailing SHA. I
> also suggested creating a tag for the beginning of
On Fri, Jan 10, 2020 at 11:45 AM Jakub Jelinek wrote:
>
> Hi!
>
> As I said earlier, one thing I find useful in svn compared to git are
> the monotonically increasing revision numbers that we at Red Hat e.g. use
> in our gcc bisect seed but I find it useful even in bugzilla everyday use.
>
> With
On Fri, Jan 10, 2020 at 10:09:08PM +0400, Joel Brobecker wrote:
> > > 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 rNN - ), and somewhere
On Fri, Jan 10, 2020 at 05:47:16PM +, Joseph Myers wrote:
> > Ok, so what about basepoints instead?
>
> That seems a better name to me.
Ok.
> > > 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 / -
> > > 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
> > 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-$
On Fri, 10 Jan 2020, Jakub Jelinek wrote:
> > 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.
>
> Ok, so what about basepoints instead?
That seems a bett
On Fri, Jan 10, 2020 at 05:05:04PM +, Joseph Myers wrote:
> 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;
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/
Hi!
As I said earlier, one thing I find useful in svn compared to git are
the monotonically increasing revision numbers that we at Red Hat e.g. use
in our gcc bisect seed but I find it useful even in bugzilla everyday use.
With the help of various folks on IRC, I have something that seems to work
22 matches
Mail list logo
