Re: [PATCH 2/3] git-bundle: die if a given ref is not included in bundle

From: Junio C Hamano <junkio@cox.net>
Date: Mar 11, 2007, 01:29 UTC
Message-ID: <7vy7m4y3cn.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0703110201450.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Basically, I am saying that this whole bundle concept is not thought 
> through, that it is too loosely defined, and that it will result in unmet 
> expectations sooner or later. (Which usually means sooner.)

Earlier I thought you said that bundle had a clearly defined semantics, which I did not quite understand, but now you are agreeing with me...

Show 5 quoted lines

> So, either we have to rethink how to handle prerequisites (so that only 
> those are checked which are strictly necessary for _the one_ ref you are 
> updating), or we have to make it _very_ obvious to (human) users of 
> git-bundle that you should _not_ bundle two unrelated -- or only remotely 
> related -- refs into one bundle.

I've been wondering if we can define prereqs per listed head.