Re: git commit guidelines for gnulib

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Bruno Haible on 9/17/2007 5:12 PM:
> 
> I would like to avoid using "git checkout" to switch from one branch to
> another in the same directory. Simply, I'm more comfortable working in
> different directories. I assume it makes it easier to remember what is where,
> and to avoid doing mistakes. Right now, I use 5 checkouts of gnulib:
>   gnulib-cvs
>   gnulib-work
>   gnulib-unistring
>   gnulib-modified
>   gnulib-manytests
> and more on demand. But I obviously don't want to have 5 copies of the large
> git repository, only 5 checkouts.

I think the easiest way to do this is with git-clone.  First, grab the
entire repository:

$ git clone git://git.sv.gnu.org/gnulib

Then create your topic clone, which shares as much repository information
as possible with the original, but can reside on a different branch:

$ git clone -l -s -n gnulib gnulib-modified
$ cd gnulib-modified && git checkout -b modified

> - Does someone have a tutorial how to work with git in this setting?

http://git.or.cz/gitwiki/GitFaq may prove helpful.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG7xFd84KuGfSFAYARAvHGAJ4yIeaLSlCUXm0GpYr5+vKLu5ooGACfWO56
OfXgI0mNcZJuYnWEqby79eY=
=zG4g
-----END PGP SIGNATURE-----