Re: git bug? + question

[Josef Weidendorfer <Josef.Weidendorfer@gmx.de>]

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.
But why not support fetch lines in [branch.*] sections?

Ie. instead of

>       [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
>               merge = remotes/gitster/master
>       [branch."next"]
>               remote = gitster
>               merge = remotes/gitster/next

make your config look like

       [remote."gitster"]
               url = gitster.example.com:/home/junio/git.git/
       [branch."master"]
               remote = gitster
               fetch = heads/master:remotes/gitster/master
               merge = remotes/gitster/master
       [branch."next"]
               remote = gitster
               fetch = heads/next:remotes/gitster/next
               merge = remotes/gitster/next

A fetch line in [branch.*] means: Also fetch this refspec in
addition to the refspecs specified in the remote section.
Problem being that "git fetch gitster" does nothing anymore :-(

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