[PATCH] histedit: pick an appropriate base changeset by default (BC)
Martin von Zweigbergk
martinvonz at google.com
Wed Nov 25 09:12:42 CST 2015
In git, you can configure an "upstream" for your branch. That is used as a
default for histedit (rebase -i), rebase and merge. I think it makes sense
for them to default to the same thing. I know there has been resistance to
adding an upstream concept, but I think it's worth considering at least
some way of having these commands default to the same thing.
On Wed, Nov 25, 2015, 05:43 Augie Fackler <raf at durin42.com> wrote:
>
> > On Nov 25, 2015, at 3:37 AM, Gregory Szorc <gregory.szorc at gmail.com>
> wrote:
> >
> > + histeditdefault = ui.config('histedit', 'defaultrev',
> > + 'first(only(.) and not public() and not
> ::merge())')
>
> Durham, how does this compare to what FBers get from your stuff? Do you
> have any sense of how it’s better or worse?
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20151125/f40be4f7/attachment.html>
More information about the Mercurial-devel
mailing list