Re: [PATCH] remote-bzr: update old organization
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 14, 2013, 21:18 UTC
- Message-ID
- <7v4ne5i7lf.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CAMP44s16VD+Rm5J=TXxQB+pKhpzHqoxBXSSwDvi0CVW2u2J=5g@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 15 quoted lines
> I forgot to mention the main objective of the shared repo feature: > > + first/ > * first/second/foo > * first/third/foo > * first/fourth/foo > * first/fifth/foo > * first/sixth/foo > > Since in bazaar branches are repositories, we want to make it possible > for remote-bzr users to create a single remote per branch as easily as > possible (without having to duplicate huge clones). > > But as I said, without this patch, they wouldn't be able to use that > feature if they cloned with v1.8.2.
So we nuke that and have them clone from scratch? I am not saying that is bad. I just want us to be honest about the implications when including it in the ReleaseNotes.