Re: git commit guidelines for gnulib

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 > @git.sv.gnu.org:/srv/git/gnulib.git), or modify > your existing checkout to point to the new re

Re: git commit guidelines for gnulib

Eric Blake <[EMAIL PROTECTED]> writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to Simon Josefsson on 9/21/2007 7:06 AM: >> [EMAIL PROTECTED]:~/src/gnulib$ git-push --all >> fatal: The remote end hung up unexpectedly >> error: failed to push to 'git://git.sv.gnu.org/gnulib'

Re: git commit guidelines for gnulib

Simon Josefsson <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: > >> I'll post a new how-to separately, but you've prompted me to >> write the following: > > Thanks! I've updated the daily autobuilder to check out from git, seems > to be working: > > http://autobuild.josefsso

Re: git commit guidelines for gnulib

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 9/21/2007 7:06 AM: > [EMAIL PROTECTED]:~/src/gnulib$ git-push --all > fatal: The remote end hung up unexpectedly > error: failed to push to 'git://git.sv.gnu.org/gnulib' > [EMAIL PROTECTED]:~/src/gnulib$ > The git://

Re: git commit guidelines for gnulib

Jim Meyering <[EMAIL PROTECTED]> writes: > I'll post a new how-to separately, but you've prompted me to > write the following: Thanks! I've updated the daily autobuilder to check out from git, seems to be working: http://autobuild.josefsson.org/gnulib/ However, the revision isn't working any m

Re: git commit guidelines for gnulib

Hi Jim, Thanks for all these explanations. It's all convincing. I'm all for doing the switch now (assuming you won't go on vacation tomorrow :-)). Bruno

Re: git commit guidelines for gnulib

Bruno Haible <[EMAIL PROTECTED]> wrote: >> How can that go wrong? >> If you update (pull/fetch/whatever), make a change, >> and commit (locally), but don't push right away... >> Then, someone else makes a change, commits, and pushes theirs. >> After that, you pull (using cvs model), and that induce

Re: git commit guidelines for gnulib

Eric Blake wrote: > 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

Re: git commit guidelines for gnulib

-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 t

Re: git commit guidelines for gnulib

Hi Jim, Thanks for reminding us how git works; it's indeed 8 months since I last used it. Three questions though: I) About merge commits. > However, I have one strong preference that I haven't yet mentioned: > = > Be careful not to push merge commits. > =

git commit guidelines for gnulib

Simon Josefsson <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: >> Now that the cvs-to-git gateway is set up, I am ready to switch >> gnulib development to git. > > I like it. > >> There are probably tools and services (web?) that rely on having >> an actual CVS repository, bu