Vladimir Marek wrote:
> > > * To programatically find where the branching happened run
> > > hg parents -r $(hg log -b s11-sru -l 1 -r 0:tip --template '{rev}\n')
> >
> > Also:
> >
> > hg log -r "ancestor('default', 's11-sru')"
> >
> > or
> >
> > hg log -r "parents(min(branch('s11-sru')))"
>
> That's cool, I wonder why 'hg help revisions' does not mention something
> like this?
Dunno. "hg help revsets" is where this comes from. The text in "hg help
revisions" may have changed since 1.8, too.
> > > * Copy changeset X from default to SRU.
> > > hg log -p -r X | hg import --no-commit -
> > > Then normally hg diff/hg commit/....
> >
> > Probably better to use "hg export -g X" instead of "hg log".
>
> Hmm, originally I didn't want to use 'hg export' as that kept commit
> date, user and message from the source changeset. But then I found
> --no-commit, so this should not be a problem. I'll try and fix the doc.
The key, IMO, is -g. You could use hg diff -c X, too, but you want to make
sure that file deletion, copy, and move are all recorded properly.
Danek
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
