Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 28, 2005, 15:56 UTC
Message-ID: <Pine.LNX.4.58.0507281747320.29968@wgmdd8.biozentrum.uni-wuerzburg.de>
In-Reply-To: <20050728153506.GL14229@pasky.ji.cz>

Hi,

On Thu, 28 Jul 2005, Petr Baudis wrote:

Show 13 quoted lines

> Dear diary, on Thu, Jul 28, 2005 at 03:07:01PM CEST, I got a letter
> where Johannes Schindelin <Johannes.Schindelin@gmx.de> told me that...
>
> > On Thu, 28 Jul 2005, Petr Baudis wrote:
> >
> > > See above. I would much rather see more flexible git-send-pack. Junio,
> > > what about changing its [heads]* parameter e.g. to
> > > [remotehead[:localhead]]* ?
> >
> > IMHO this opens the door for shooting in your own foot. Isn't it much too
> > easy to make a mistake with that syntax?
>
> What mistake?

To mix up different branches. With that syntax you can easily push changes onto the wrong head.

I might well be wrong here, but I think the most common usage for git-push is to update a public repository, which is done by one or just a few maintainer(s), in which case it is no problem to enforce localhead=remotehead. BTW, this whole multihead mess applies only to Jeffs anyway :-)

I just do not see a high demand for mappings of remote and local HEAD names, but rather a high potential of making mistakes (after all, it is not the machine which makes mistakes, it's the human operator).

> If you want the holes in your knowledge showing up try teaching
> someone.  -- Alan Cox

I like that one.

Ciao, Dscho