absorb extension: Suggestions

[Craig Ozancin]

I have thought the same thing. Absorb has been a bit of a hit/miss for me.
Absorb is very impressive, but all to often there are changes that it does
not identify for a specific revision and I end up using histedit to get
them in place. I would love to be able to specify a target changeset. This
might make more sense for the amend command however as in:

     hg amend -r sid/hash -i

On Tue, Jan 15, 2019 at 8:49 AM Marcus Harnisch <marcus.harnisch at verilab.com>
wrote:

> Hi all
>
> Using the absorb extension for the first time left me impressed. But even
> good things can be improved. I noticed the following (relatively minor) UI
> issues:
> 1. It is easy to miss the fact that there are changes for which a suitable
> past changeset could not be found. Perhaps add a little note at the end
> stating this explicitly.
> 2. In some cases I know exactly which revision should be amended with my
> changes, while the algorithm might believe differently. Interactive mode
> helps but could be rather inconvenient in simple cases which at the same
> time might affect many files (confirmation needed for each file). Would it
> make sense to be able to specify a revision explicitly?
>
> Thanks,
> Marcus
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20190121/8be1331f/attachment-0002.html>