Re: git commit guidelines for gnulib

[Bruno Haible]

Eric Blake wrote:
> The git:// protocol is read-only.  You have to use the ssh protocol
> (git+ssh is longhand for ssh).
> ...
> To check in, you need to either start a clone with ssh syntax (git clone
> <your-savannah-username>@git.sv.gnu.org:/srv/git/gnulib.git), or modify
> your existing checkout to point to the new remote.  If you are using git
> 1.5.3 or newer, then see my suggestions here:
> http://lists.gnu.org/archive/html/bug-gnulib/2007-09/msg00141.html

Thanks for mentioning this. It's worth documenting one of these approaches
in the README. Since the easiest among them is the clone with ssh URL, I'm
adding this:


2007-09-24  Bruno Haible  <address@hidden>

        * README: Update git instructions.

*** README.orig 2007-09-25 02:00:28.000000000 +0200
--- README      2007-09-25 01:40:46.000000000 +0200
***************
*** 217,222 ****
--- 217,230 ----
  Or, if you prefer the CVS-like 'cogito' frontend to plain 'git':
    $ cg clone git://git.sv.gnu.org/gnulib
  
+ For a read-write checkout you need to have a login on savannah.gnu.org and be
+ a member of the gnulib project at http://savannah.gnu.org/projects/gnulib .
+ Then, instead of the URL
+   git://git.sv.gnu.org/gnulib
+ use the URL
+   ssh://<user>@git.sv.gnu.org/srv/git/gnulib
+ where <user> is your login name on savannah.gnu.org.
+ 
  git resources:
    Overview: http://en.wikipedia.org/wiki/Git_(software)
    Homepage: http://git.or.cz/