Re: Recommended work flow with git to send in patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 28, 2010 at 7:20 PM, Jakub Narebski <jnareb@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]