Re: git conversion in progress

On Wed, 22 Jan 2020, Jakub Jelinek wrote: >> The rsync.html page can be removed too, since that was a way to download >> the entire svn repo. With git clone, you get the entire repo, so rsync >> isn't needed anymore. > I disagree, it isn't just about downloading a svn repo, but mailing list > arch

Re: git conversion in progress

On Wed, Jan 22, 2020 at 11:41:22AM -0600, Peter Bergner wrote: > On 1/22/20 3:26 AM, Gerald Pfeifer wrote: > > On Mon, 13 Jan 2020, Joseph Myers wrote: > >> In addition, once git.html is more complete (has the list of branches > >> added, at least) we need to update the GCC home page to link to th

Re: git conversion in progress

On 1/22/20 3:26 AM, Gerald Pfeifer wrote: > On Mon, 13 Jan 2020, Joseph Myers wrote: >> In addition, once git.html is more complete (has the list of branches >> added, at least) we need to update the GCC home page to link to the new >> pages in place of those for SVN, redirect the old pages to th

Re: git conversion in progress

On Mon, 13 Jan 2020, Joseph Myers wrote: > In addition, once git.html is more complete (has the list of branches > added, at least) we need to update the GCC home page to link to the new > pages in place of those for SVN, redirect the old pages to the new ones, > and generally update references

Re: git conversion in progress

All (annotated) release tags are misnamed. For example, refs/tags/releases/gcc-9.2.0 is really named gcc_9_2_0_release: $ git cat-file -p releases/gcc-9.2.0 object a0c06cc27d2146b7d86758ffa236516c6143d62c type commit tag gcc_9_2_0_release tagger Jakub Jelinek 1565595539 +020

Re: git conversion in progress

On Thu, 16 Jan 2020, Jonathan Wakely wrote: > On Thu, 16 Jan 2020 at 09:55, Georg-Johann Lay wrote: >> Hi, the front page reads "Our sources are readily and freely available >> via SVN...", similar recommendation for SVN in > Yes, it's been said more than once that the web pages will be updated >

Re: git conversion in progress

On Thu, 16 Jan 2020 at 09:55, Georg-Johann Lay wrote: > > Am 11.01.20 um 02:18 schrieb Joseph Myers: > > I encourage people to continue to work on improving the documentation for > > using git with GCC > > Hi, the front page reads "Our sources are readily and freely available > via SVN...", simila

Re: git conversion in progress

Am 11.01.20 um 02:18 schrieb Joseph Myers: I encourage people to continue to work on improving the documentation for using git with GCC Hi, the front page reads "Our sources are readily and freely available via SVN...", similar recommendation for SVN in https://gcc.gnu.org/snapshots.html Jo

Re: git conversion in progress

Hi, On Tue, Jan 14 2020, Andreas Schwab wrote: > On Jan 14 2020, Martin Jambor wrote: > >> Hi, >> >> On Tue, Jan 14 2020, Andreas Schwab wrote: >>> On Jan 14 2020, Georg-Johann Lay wrote: >>> git clone --reference original-gcc ... >>> >>> Don't use --reference. It is too easy to lose work if

Re: git conversion in progress

On Tue, Jan 14, 2020 at 06:06:36PM +, Joseph Myers wrote: > On Tue, 14 Jan 2020, Jason Merrill wrote: > > > I notice that git.html on the website doesn't match what's currently in > > wwwdocs git, is automatic updating broken? > > /www/gcc/wwwdocs-checkout/cgi-bin/gcc-gitref.cgi had local cha

Re: git conversion in progress

On Tue, 14 Jan 2020, Jason Merrill wrote: > I notice that git.html on the website doesn't match what's currently in > wwwdocs git, is automatic updating broken? /www/gcc/wwwdocs-checkout/cgi-bin/gcc-gitref.cgi had local changes (committed, but not reverted in that checkout before they were commi

Re: git conversion in progress

On Tue, Jan 14, 2020 at 9:56 AM Andreas Schwab wrote: > On Jan 14 2020, Martin Jambor wrote: > > > On Tue, Jan 14 2020, Andreas Schwab wrote: > >> On Jan 14 2020, Georg-Johann Lay wrote: > >> > >>> git clone --reference original-gcc ... > >> > >> Don't use --reference. It is too easy to lose w

Re: git conversion in progress

On Tue, 14 Jan 2020, Richard Earnshaw wrote: > Well it's likely that the server would have to repack the objects on the > fly to supply just one branch; and it does that less well than the base > pack). So you'd probably end up with a much larger initial download > than just fetching the entire h

Re: git conversion in progress

On Tue, 14 Jan 2020, Georg-Johann Lay wrote: > A branch called branchname can be checked out with the following command: > > git clone -b branchname ... > > Referring to this as "checking out" is confusing IMO, because it may be > confused with > git checkout -b branchname > > Whereas t

Re: git conversion in progress

On Tue, 14 Jan 2020, Georg-Johann Lay wrote: > In order to set user.name and user.email, the doc is using --global. At least > for me, the latter is not what I want because I am using git in other contexts > than contributing to GCC (and am using different e-mail then). Using --global is the sim

Re: git conversion in progress

On Tue, 14 Jan 2020 at 14:28, Martin Jambor wrote: > > Hi, > > On Tue, Jan 14 2020, Andreas Schwab wrote: > > On Jan 14 2020, Georg-Johann Lay wrote: > > > >> git clone --reference original-gcc ... > > > > Don't use --reference. It is too easy to lose work if you don't know > > what you are doing

Re: git conversion in progress

On Jan 14 2020, Martin Jambor wrote: > Hi, > > On Tue, Jan 14 2020, Andreas Schwab wrote: >> On Jan 14 2020, Georg-Johann Lay wrote: >> >>> git clone --reference original-gcc ... >> >> Don't use --reference. It is too easy to lose work if you don't know >> what you are doing. > > What are the ris

Re: git conversion in progress

Hi, On Tue, Jan 14 2020, Andreas Schwab wrote: > On Jan 14 2020, Georg-Johann Lay wrote: > >> git clone --reference original-gcc ... > > Don't use --reference. It is too easy to lose work if you don't know > what you are doing. What are the risks, assuming I won't delete the referenced repo whic

Re: git conversion in progress

On 14/01/2020 13:00, Jonathan Wakely wrote: On Tue, 14 Jan 2020 at 11:37, Georg-Johann Lay wrote: Am 14.01.20 um 12:34 schrieb Andreas Schwab: On Jan 14 2020, Georg-Johann Lay wrote: git clone --reference original-gcc ... Don't use --reference. It is too easy to lose work if you don't kn

Re: git conversion in progress

On Tue, 14 Jan 2020 at 11:37, Georg-Johann Lay wrote: > > Am 14.01.20 um 12:34 schrieb Andreas Schwab: > > On Jan 14 2020, Georg-Johann Lay wrote: > > > >> git clone --reference original-gcc ... > > > > Don't use --reference. It is too easy to lose work if you don't know > > what you are doing. >

Re: git conversion in progress

On Jan 14 2020, Jakub Jelinek wrote: > On Tue, Jan 14, 2020 at 12:34:13PM +0100, Andreas Schwab wrote: >> On Jan 14 2020, Georg-Johann Lay wrote: >> >> > git clone --reference original-gcc ... >> >> Don't use --reference. It is too easy to lose work if you don't know >> what you are doing. > >

Re: git conversion in progress

On Tue, Jan 14, 2020 at 12:34:13PM +0100, Andreas Schwab wrote: > On Jan 14 2020, Georg-Johann Lay wrote: > > > git clone --reference original-gcc ... > > Don't use --reference. It is too easy to lose work if you don't know > what you are doing. Wouldn't git clone --reference original-gcc --dis

Re: git conversion in progress

On Jan 14 2020, Georg-Johann Lay wrote: > git clone --reference original-gcc ... Don't use --reference. It is too easy to lose work if you don't know what you are doing. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1

Re: git conversion in progress

Am 14.01.20 um 12:34 schrieb Andreas Schwab: On Jan 14 2020, Georg-Johann Lay wrote: git clone --reference original-gcc ... Don't use --reference. It is too easy to lose work if you don't know what you are doing. Andreas. Well, then it should not be proposed in git.html then? There may b

Re: git conversion in progress

On Jan 14 2020, Georg-Johann Lay wrote: > or can be achieved by > > git config [--global] core.editor="...". Space instead of = between key and value. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for somethi

Re: git conversion in progress

On 14/01/2020 11:01, Georg-Johann Lay wrote: > Am 11.01.20 um 02:18 schrieb Joseph Myers: >> I encourage people to continue to work on improving the documentation for >> using git with GCC >> ( and >>

Re: git conversion in progress

Am 11.01.20 um 02:18 schrieb Joseph Myers: I encourage people to continue to work on improving the documentation for using git with GCC ( and list some of the things that it seems

Re: git conversion in progress

Am 11.01.20 um 02:18 schrieb Joseph Myers: I encourage people to continue to work on improving the documentation for using git with GCC ( and list some of the things that it seems

Re: git conversion in progress

The repository is now open for commits. Snapshot generation and DATESTAMP updates from cron are now enabled. I intend to work on the scripts to update online documentation, but they aren't done yet. *Please help with updating documentation for using git with GCC*.

Re: git conversion in progress

On Sat, 11 Jan 2020, Joseph Myers wrote: > the older test conversions 1 through 7). Some cron jobs may be re-enabled > before then, subject to testing (I have git changes to gcc_release ready, > for example, for testing snapshot generation), but the DATESTAMP updates > won't be enabled until t

Re: git conversion in progress

On Sat, 11 Jan 2020, Thomas Koenig wrote: > Hm... I just hope this is a one-time effect, and isn't an indication > that git uses much more resources, server-side, so the current > infrastructure is not up to the task. Is git that much more > resource hungry than svn? Or is this unrelated? I thin

Re: git conversion in progress

Thomas Koenig : > Hm... I just hope this is a one-time effect, and isn't an indication > that git uses much more resources, server-side, so the current > infrastructure is not up to the task. Is git that much more > resource hungry than svn? Or is this unrelated? Almost certanly unrelated. In nor

Re: git conversion in progress

Hi Martin,   It does not for me (something about public key rejected), but then I am a complete novice at using git, so I am more or less doing vodoo git here. Please paste the error message you face? Currently, gcc.gnu.org is totally under water, even accessing the wiki leads to a timeout, s

Re: git conversion in progress

On Sat, 11 Jan 2020, Thomas Koenig wrote: > Am 11.01.20 um 15:39 schrieb Joseph Myers: > > This conversion is now in place, read-only for checking purposes. I've > > done all the usual validation, including in particular checking branch > > tips and tags against SVN. > > Is checkout via git+ssh

Re: git conversion in progress

On 1/11/20 5:33 PM, Thomas Koenig wrote: Am 11.01.20 um 15:39 schrieb Joseph Myers: This conversion is now in place, read-only for checking purposes.  I've done all the usual validation, including in particular checking branch tips and tags against SVN. Is checkout via git+ssh supposed to work

Re: git conversion in progress

On Jan 11 2020, Richard Earnshaw wrote: > $ git ls-remote|grep vendors|sed -r "s|.*vendors/([^/]+).*|\1|"|sort|uniq git ls-remote URL "*/vendors/*" | ... Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for some

Re: git conversion in progress

On 11/01/2020 16:33, Thomas Koenig wrote: > Am 11.01.20 um 15:39 schrieb Joseph Myers: >> This conversion is now in place, read-only for checking purposes.  I've >> done all the usual validation, including in particular checking branch >> tips and tags against SVN. > > Is checkout via git+ssh supp

Re: git conversion in progress

On Jan 11 2020, Richard Earnshaw wrote: > Once you have a checkout, "git ls-remote" will show all the refs on the > server. You don't need a checkout, git ls-remote works on a remote URL. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF7

Re: git conversion in progress

Am 11.01.20 um 15:39 schrieb Joseph Myers: This conversion is now in place, read-only for checking purposes. I've done all the usual validation, including in particular checking branch tips and tags against SVN. Is checkout via git+ssh supposed to work for this? It does not for me (something

Re: git conversion in progress

On Sat, 11 Jan 2020, Richard Earnshaw wrote: > On 11/01/2020 14:58, Jakub Jelinek wrote: > > On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote: > >> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch > >> > >> Works > >> > >> Or for tags s/heads/t

Re: git conversion in progress

On 11/01/2020 15:01, Richard Earnshaw wrote: > On 11/01/2020 14:58, Jakub Jelinek wrote: >> On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote: >>> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch >>> >>> Works >>> >>> Or for tags s/heads/tags/ >>

Re: git conversion in progress

On 11/01/2020 14:58, Jakub Jelinek wrote: > On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote: >> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch >> >> Works >> >> Or for tags s/heads/tags/ > > Indeed, this works, but if one doesn't know what b

Re: git conversion in progress

On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote: > https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch > > Works > > Or for tags s/heads/tags/ Indeed, this works, but if one doesn't know what branches there are for particular vendor or what ven

Re: git conversion in progress

On 11/01/2020 14:51, Richard Earnshaw wrote: > On 11/01/2020 14:49, Richard Earnshaw wrote: >> On 11/01/2020 14:48, Jakub Jelinek wrote: >>> On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote: > On 11/01/2020 01:18, Joseph Myers wrote: >> The GCC SVN repository is now read-only fo

Re: git conversion in progress

On 11/01/2020 14:49, Richard Earnshaw wrote: > On 11/01/2020 14:48, Jakub Jelinek wrote: >> On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote: On 11/01/2020 01:18, Joseph Myers wrote: > The GCC SVN repository is now read-only for the move to git, as is the > old > git-

Re: git conversion in progress

On 11/01/2020 14:48, Jakub Jelinek wrote: > On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote: >>> On 11/01/2020 01:18, Joseph Myers wrote: The GCC SVN repository is now read-only for the move to git, as is the old git-svn mirror; the cron job updating that mirror has been dis

Re: git conversion in progress

On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote: > > On 11/01/2020 01:18, Joseph Myers wrote: > > > The GCC SVN repository is now read-only for the move to git, as is the > > > old > > > git-svn mirror; the cron job updating that mirror has been disabled, as > > > have gccadmin's cr

Re: git conversion in progress

On Sat, 11 Jan 2020, Richard Earnshaw wrote: > On 11/01/2020 01:18, Joseph Myers wrote: > > The GCC SVN repository is now read-only for the move to git, as is the old > > git-svn mirror; the cron job updating that mirror has been disabled, as > > have gccadmin's cron jobs updating DATESTAMP, gen

Re: git conversion in progress

On 11/01/2020 01:18, Joseph Myers wrote: > The GCC SVN repository is now read-only for the move to git, as is the old > git-svn mirror; the cron job updating that mirror has been disabled, as > have gccadmin's cron jobs updating DATESTAMP, generating snapshots and > updating online documentation