On Tue, Jan 14, 2020 at 12:04:04PM +0300, Roman Zhuykov wrote: > It was a bit confusing to see "git descr" here in posted patch and "git > gcc-descr" actually committed.
That was an IRC request from Richard Earnshaw. > Moreover "git gcc-descr" doesn't work for me with old git: > > ~$ git --version > git version 2.7.4 > ~$ git clone git://gcc.gnu.org/git/gcc test > <...> > ~$ cd test/ > ~/test$ > ~/test$ ./contrib/gcc-git-customization.sh > <...> > ~/test$ git describe --all --abbrev=40 --match 'basepoints/gcc-[0-9]*' > origin/master > basepoints/gcc-10-5938-gedabbec31e3bfc9a9757f80c8610706ed00e5a1a > ~/test$ git gcc-descr origin/master > ~/test$ > > So, locally I have to fix alias removing "tags/" part in commands like "sed > -n 's,^tags/basepoints/gcc-,r,p'". > > With new git v2.24.0 alias works fine. Investigation shows it was changed > inside git by commit > https://github.com/git/git/commit/1bba00130a1a0332ec0ad2f878a09ca9b2b18ee2 > two years ago. So, only git v2.16.2, v2.17.0 or newer versions correctly run > current alias. Not sure we want to bother about supporting older versions. Note, for the scripts running on sourceware I also had to remove those tags/ part, but thought it is because of running against the bare repo. We could change those into ^\\(tags/\\)\\?basepoints/gcc- etc. (and adjust the \\1. I'll post a patch. > PS. We at ISPRAS see that for ~28 hours (11 Jan 2020, 18:00 UTC - 12 Jan > 2020, 22:00 UTC) our servers haven't received any gcc mailing list letters, > but they are available at https://gcc.gnu.org/ml/ archives (totally 6 mails > on gcc@ and 16 on gcc-patches@ were lost). Looking also at obviously > corruptedhttps://gcc.gnu.org/ml/gcc-patches/2020-01/msg00674.html it is > reasonable to assume that it was some worldwide issue because of high "git > clone" server load, and I wonder not to see any discussion here. Strange, I certainly am receiving gcc mailing list mails. Jakub
