Re: Changing source code control systems

> From: Paul Smith <[email protected]>
> Cc: [email protected]
> Date: Fri, 18 Jan 2013 06:56:29 -0500
> 
> On Fri, 2013-01-18 at 09:46 +0200, Eli Zaretskii wrote:
> > There's nothing on Savannah about how to clone the git repo for
> > developers who have write access.  Can you provide the missing info
> > here?
> 
> Hm.  Weird.  I'll file a bug with Savannah.  Anyway, try this:
> 
>         git clone [email protected]:/srv/git/make.git
> 
> This puts the local repo at "./make".  If you want it to be named
> something else, use:
> 
>         git clone [email protected]:/srv/git/make.git make-other
> 
> After that it's the same procedure as before (see README.git) to build.
> Let me know if this does not work.

It worked, after I configured git to use my existing ssh keys that
Savannah knows about.  (That wasn't trivial to do on Windows, and a
quick Google search didn't find anything that worked.)

I pushed a simple change in ChangeLog, just to be sure I know how to
do that, please see if I did something wrong.  (I never pushed
anything to any git repository until now, only pulled read-only
copies.)  It might be a good idea to add a short section to README.git
with a simple workflow for developers who are not used to using git,
to avoid any breakage that incorrect usage might cause.

Thanks.