[PATCH 5 of 6] rebase: demonstrate behavior with requiredest and pull --rebase
Jun Wu
quark at fb.com
Wed Mar 29 13:55:51 EDT 2017
Excerpts from Ryan McElroy's message of 2017-03-29 11:38:00 +0100:
> drawdag.py I think you mean?
>
> I suppose a nice thing about drawdag is that you see the dag being
> created so its more obvious what's going on without graph logs, but is
> it worth a re-send do you think? These tests are fairly straightforward,
> and the exact contents of the files matter so they cause conflicts
> sometimes and not other times.
Probably not. I just want to advertise tools like "debugbuilddag" and
"drawdag". So new tests can use them.
I should probably just update the wiki.
>
> >
> >> + pulling from $TESTTMP/repo
> >> + searching for changes
> >> + adding changesets
> >> + adding manifests
> >> + adding file changes
> >> + added 1 changesets with 2 changes to 2 files (+1 heads)
> >> + abort: you must specify a destination
> >> + (use: hg rebase -d REV)
> >> + [255]
> >> +
More information about the Mercurial-devel
mailing list