Re: Recommended work flow with git to send in patches

From: Tong Sun <suntong@cpan.org>
Date: Jul 27, 2010, 19:48 UTC
Message-ID: <AANLkTi=psuiq-GP9zV=pY6swNAUF-MwJt6COrNDVDLqu@mail.gmail.com>
In-Reply-To: <m3y6cwkew7.fsf@localhost.localdomain>

On Tue, Jul 27, 2010 at 1:35 PM, Jakub Narebski <jnareb@gmail.com> wrote:

> Doesn't GRML have web page / wiki page for developers?

Yes, http://grml.org/git/, but it is kind of reference book style, doesn't cover much on the work flow, especially on the topic of no-writing-privilege user contributing back.

Show 6 quoted lines

>> - do initial git pull into grml-debootstrap
>>
>>   git pull git://git.grml.org/grml-debootstrap master
>
> Why not git-clone (possibly shallow, if you are working on one-shot
> patch or patch series)?

Ok, to explain it, I have to touch upon my "life long story" of using git. Long story short on this, the recommended work flow that I searched and found from the Inet was to do 'git clone' from web then 'git clone' a local working copy. Here is my trying log:

# Download the latest version of the repository without downloading all the history, using "shallow checkouts".

  git clone --depth 1 git://git.grml.org/grml-debootstrap.git

create working repo:

  $ git-clone --depth 1 grml-debootstrap grml-debootstrap.working
  Initialized empty Git repository in
/export/repositories/gitwork/grml/grml-debootstrap.working/.git/
  fatal: attempt to fetch/clone from a shallow repository
  ^^^^^^^^^^^^^^^

Seeing that fatal error, and not knowing where to get help from, I just gave up the 'git clone' approach. Please be specific (with git commands), how would I use 'git clone' for working on one-shot patch or patch series.

Got to run, will comment on the rest later.

thanks