Hi,

On Sat, 9 Feb 2008, Martin Langhoff wrote:

quoted text
> On Feb 9, 2008 12:50 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 
> > The problem is that the local side cannot tell
> 
> The local side has the remote refs if the client has fetched recently, 
> so it might be able to tell in some cases. Not with authority (things 
> may have changed on the server side...) but the client might be able to 
> say something less alarming.

But if it was not fetched recently?  I think that what you suggest is too 
tricky (IOW too prone to break).

quoted text
> > Another way to "solve" this issue, of course, is to use the remote 
> > layout. I did the switchover myself some time ago; it was hard at 
> > first, since I was so used to just check out the branches I just 
> > fetched.  But in the long run the distinction between local and 
> > tracking branches made life much easier for me.
> 
> What do you mean with "the remote layout"? I am using "remotes"+tracking 
> branches as far as I can tell...

I mean keeping most branches purely as tracking branches.  Whenever you 
are done with one branch, you delete the local branch.

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html