Look into a bundle file

Alpár Jüttner alpar at cs.elte.hu
Sat Mar 22 16:11:39 CDT 2008


Hi,

Thank you for the extension, it's fine, it does what I want.
I just mention that commands.logopts, seems to be a very recent feature,
it was commited less than a month ago and it is not yet in the hg-stable
repo.

But am I right that the behavior with the merge commit
is a bug? (I haven't checked it with a latest version, only with 0.9.5).
Shall I file it in the bug-tracker?

Best regard,
Alpar


On Sat, 2008-03-22 at 15:03 -0400, John Mulligan wrote:
> On Friday 21 March 2008, Alpár Jüttner wrote:
> > Hi,
> >
> > I tried this:
> >
> >         $ hg init empty
> >         $ cd empty
> >         $ hg in ../random_seeding.bundle
> >         comparing with ../random_seeding.bundle
> >         abort: unknown parent 70f3967ca6eb!
> >         $ hg pull -r 70f3967ca6eb ../main
> >         ...
> >         $ hg in ../random_seeding.bundle
> >         comparing with ../random_seeding.bundle
> >         searching for changes
> >         changeset:   102:81563e019fa4
> >         tag:         tip
> >         user:        Balazs Dezso <xyz at xyz>
> >         date:        Thu Mar 20 17:15:35 2008 +0100
> >         summary:     Seeding random sequence
> >
> > This is quite tedious, but it is at least something. However, I also
> > tried it to a bundle file having more than one parents (actually, for a
> > merge commit),and I got this:
> >
> >         $ hg init empty
> >         $ cd empty
> >         $ hg in ../merge.hg
> >         comparing with ../merge.hg
> >         abort: unknown parent cdbba181b786!
> >         $ hg pull -r cdbba181b786 ../main
> >         pulling from ../main
> >         requesting all changes
> >         adding changesets
> >         adding manifests
> >         adding file changes
> >         added 104 changesets with 235 changes to 86 files
> >         (run 'hg update' to get a working copy)
> >         $ hg in ../merge.hg
> >         comparing with ../merge.hg
> >         abort: unknown parent cdbba181b786!
> >
> > What to do then? Is it a bug?
> 
> Normally, the bundle repositories skip over changesets that are already a part 
> of the base repository and never records what was part of the bundle 
> (AFAICT). Since I had been looking at the bundle repository module lately I 
> thought this would be an interesting problem to tackle. I created a very 
> hacky extension that will list the contents of the bundle regardless of its 
> status as part of the base repo.
> 
> I've attached the extension to this message. I've not tested it on a repo with 
> a changeset with two parents so please let me know if that breaks it for you.
> 
> Load the extension as usual, and from your main repository run: 
>   hg bundlecontents /path/to/bundle.hg
> 
> I don't plan on trying to get any of the changes I made merged, so please 
> excuse the hackery. :-)
> 
> >
> > Best regards,
> > Alpar
> >
> > On Fri, 2008-03-21 at 20:31 +0000, Alpár Jüttner wrote:
> > > Dear All,
> > >
> > > Could you tell me how to look into a bundle file?
> > > I know this:
> > >
> > > hg in bundle.hg
> > >
> > > but what to do if the changesets are already in my repo?
> > >
> > > For example, someone send me a bundle file in an e-mail, and a couple of
> > > months later I would like find out which changeset we are discussing in
> > > that e-mail thread.
> > >
> > > Is there an easy way to extract at least the changeset ids from a bundle
> > > file?
> > >
> > > Best regards,
> > > Alpar
> > >
> > >
> > > _______________________________________________
> > > Mercurial mailing list
> > > Mercurial at selenic.com
> > > http://selenic.com/mailman/listinfo/mercurial
> >
> > _______________________________________________
> > Mercurial mailing list
> > Mercurial at selenic.com
> > http://selenic.com/mailman/listinfo/mercurial
> 
> 




More information about the Mercurial mailing list