Re: [PATCH 2/3] git-bundle: die if a given ref is not included in bundle
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 10, 2007, 16:53 UTC
- Message-ID
- <Pine.LNX.4.63.0703101749270.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <45F2D955.8050800@gmail.com>
Hi,
On Sat, 10 Mar 2007, Mark Levedahl wrote:
Show 10 quoted lines
> Johannes Schindelin wrote: > > > IMHO saying "master ^master" should blow into the user's face. If she > > says "I want it" _and_ "I don't want it", she should sorta expect it > > not to work. > > [...] > > As long as the lists are syntactically acceptable (all exist), we should > just create the bundle with the given refs and prerequisites.
So, what do you do if some of your users do, and some others do not, have the "blue-sky" branch? If you say "git bundle create new.bundle --all -10", your bundle will list "blue-sky" as a prerequisite.
Boom.
Some of your users -- those without "blue-sky" -- will _not_ be able to fetch _anything_ from the bundle. They are lacking the prerequisites.
The semantics of git-bundle used to be so clear and sensible, since they exactly reflected what git-pack-objects would do.
Now they are no longer?
Ciao, Dscho