Re: Wishlist for a bundle-only transport mode

From: Santi Béjar <sbejar@gmail.com>
Date: Nov 23, 2007, 16:39 UTC
Message-ID: <8aa486160711230839o5db5fca1wc09a834ab3d4f053@mail.gmail.com>
In-Reply-To: <7v63ztuevk.fsf@gitster.siamese.dyndns.org>

On Nov 23, 2007 5:05 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 13 quoted lines

> "Santi Béjar" <sbejar@gmail.com> writes:
>
> >> > OK. So git push will never understand bundles.
> >>
> >> Why not?
> >
> > Sorry, I misunderstood you, because pushing to an existing
> > bundle loses information, and that is also inconsistent with pushing
> > to regular repositories.
>
> Maybe I am missing something from the discussion, but what
> information loss are you referring to?
>

Because you create an incremental bundle, so all the objects in the old bundle will not be in the new bundle. But it can be considered the natural behavior of bundles.

But anyway, pushing to an existing bundle is not very convenient (at leas for me) because it forces you to keep the bundles. I think the most convenient way would be to have remote tracking branching to record the bases for future bundles.

For now, I will do an script that behaves like the "git bundle push" that I described and then I'll report the pro/cons that it has.

Thank you all for the discussion, it was very fruitful.

Santi

P.D.: Am I the only one doing a bundle-only transport mode? If not, can you comment on the different suggestions that have been said. Thanks a lot.