Re: Allowing override of the default "origin" nickname

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 11, 2008, 21:12 UTC
Message-ID: <alpine.LSU.1.00.0801112111170.31053@racer.site>
In-Reply-To: <30e4a070801110815q1dee8f0cr7966fc2896e4c790@mail.gmail.com>

Hi,

On Fri, 11 Jan 2008, Mark Levedahl wrote:

Show 15 quoted lines

> On Jan 11, 2008 10:25 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> >
> > Mark, if this change is mainly about the fact that git doesn't allow 
> > to specify default remote to fetch for detached HEAD (and submodules 
> > use detached HEAD), why not provide "branch.HEAD.remote" etc., which 
> > would be used _only_ if we are on detached HEAD (i.e. branch has no 
> > name).
>
> Practically speaking, this would just change the name of the config 
> variable (from remotes.default to branch.HEAD.remote). However, this 
> value is used *whenever* the current branch does not have corresponding 
> branch.<name>.remote, and that is not restricted to detached heads, it 
> applies anytime the current HEAD is not a tracking branch. So, I believe 
> remotes.default better reflects this generality than does 
> branch.HEAD.remote.

Practically speaking, I have enough experience to _know_ that your solution will not help very much. It will just add to confusion.

You stated quite clearly -- _after_ I asked -- what your problem is, and I am quite certain that you _still_ have to look up _something_ (as I remarked in the email you responded to).

So it is still _utterly_ unclear to me how your patch helps anything.

Ciao, Dscho