Re: Working copy revision and push pain

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 23, 2008, 14:11 UTC
Message-ID: <alpine.LSU.1.00.0803231508320.4353@racer.site>
In-Reply-To: <47E658D3.1060104@jwatt.org>

Hi,

On Sun, 23 Mar 2008, Jonathan Watt wrote:

Show 15 quoted lines

> Johannes Schindelin wrote:
> 
> > On Sun, 23 Mar 2008, Jonathan Watt wrote:
> > 
> >> There seems to be a problem with git-push when the working copy of 
> >> the directory being pushed to came from the magic revision HEAD, but 
> >> not when the working copy came from some other revision.
> > 
> > http://git.or.cz/gitwiki/GitFaq#head-b96f48bc9c925074be9f95c0fce69bcece5f6e73
> > 
> > Sidenote: I am constantly amazed how people have no problem accepting 
> > that a CVS-Server has no working directory, but all of a sudden think 
> > that a Git-server should have one, and auto-update it.
> 
> I think you've misread my email. (Or not read it. ;-))

Well, I did.  Thank you very much.

Show 5 quoted lines

> I do not expect git-push to update the working copy of the repository 
> being pushed to. In fact my complaint would be more that it *does* 
> appear to modify the working copy (well, not so much modify the working 
> copy as get confused about which revision the working copy came from) 
> when the working copy came from HEAD.

You changed the current branch via push. HEAD is the tip of the current branch. <rhetoric>What else should happen?</rhetoric>

Your notion that the working tree has somehow a magic state that is not dependent on the current branch is somewhat strange to me.

Ciao, Dscho