From: Tong Sun <suntong@cpan.org>
Date: Wed, 28 Jul 2010 23:30:33 GMT
Subject: Re: Recommended work flow with git to send in patches
Message-ID: <AANLkTinfobkVFVfqgUV9QiExosfW=W3gAFr3DmDb1URw@mail.gmail.com>
In-Reply-To: <201007290120.05093.jnareb@gmail.com>

On Wed, Jul 28, 2010 at 7:20 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>>> If you plan to continue working on this repository, and it is not
>>> one-shot patch or patch series, it would be better (easier in the
>>> future) to use "git remote add".
>>
> . . .
> I don't think that would apply in your situation, but "git remote add"
> is used if you want to fetch changes from more than one upstream repository
> (or you want to configure repository to push into).  This is an alternative
> to one-shot "git pull <URL> <branch>" which does not save _any_ information
> about upstream you fetched (pulled) from.

Got it.

> See git-remote manpage for details.

and http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html as well.

thanks again. no more questions for now.

cheers