Re: git bug? + question

From: Josef Weidendorfer <josef.weidendorfer@gmx.de>
Date: Nov 4, 2006, 17:50 UTC
Message-ID: <200611041850.20136.Josef.Weidendorfer@gmx.de>
In-Reply-To: <7vk62bxvtx.fsf@assigned-by-dhcp.cox.net>

On Saturday 04 November 2006 13:03, Junio C Hamano wrote:

Show 21 quoted lines

> Josef Weidendorfer <Josef.Weidendorfer@gmx.de> writes:
> 
> > On Friday 03 November 2006 10:46, Karl Hasselström wrote:
> >> Hmm. How about changing the meaning of "remote" slightly? Like this:
> >
> > That's not good, as it changes existing config meaning.
> >...
> > Other option: Introduce "fetchonly" line which ignores the original
> > fetch lines in the remote section.
> >
> >        [remote."gitster"]
> >                url = gitster.example.com:/home/junio/git.git/
> >                fetch = heads/master:remotes/gitster/master
> >                fetch = heads/next:remotes/gitster/next
> >        [branch."master"]
> >                remote = gitster
> >                fetchonly = heads/master:remotes/gitster/master
> >                merge = remotes/gitster/master
> 
> That is a regression in that now I need to fetch twice (in the
> above example, in reality four).

Hmm. You do not need to use it. However, there are use cases for this.

For example, I am mostly interested in what's new on the next and master branch in the git repository. There is no need for me to always fetch pu or maint.

So I can use (I am behind a firewall):

[remote "origin"]
        url = http://www.kernel.org/pub/scm/git/git.git
        fetch = master:origin
        fetch = maint:maint
        fetch = next:next
        fetch = todo:todo
        fetch = +pu:pu

[branch "master"]
        remote = origin
        fetchonly = master:origin
	fetchonly = next:next
        merge = origin

and get master and next with a "git fetch" when on master, and "git fetch origin" would fetch all branches.