all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 34944@debbugs.gnu.org
Subject: bug#34944: 27.0.50; FR: support amend in vc-hg
Date: Sat, 6 Apr 2019 15:54:08 +0200	[thread overview]
Message-ID: <CAArVCkQz41zsa60jaZxQGWK92pPGeFLE7hVH7C42HoZDVJebuA@mail.gmail.com> (raw)
In-Reply-To: <9b5b5852-6b37-59d9-146f-371a213e7045@yandex.ru>

Am Mi., 3. Apr. 2019 um 02:33 Uhr schrieb Dmitry Gutov <dgutov@yandex.ru>:
>
> On 22.03.2019 12:44, Philipp Stephani wrote:
> >
> > The Git integration for vc.el supports amending commits via a magic
> > changelog header.  Mercurial has the same functionality, see
> > https://www.mercurial-scm.org/wiki/EditingHistory#Amending_the_latest_changeset_with_commit_--amend.
> > If would be great to support this in Emacs as well.  Maybe the Git
> > approach could even move into main VC, and made available to all
> > backends that support amending?
>
> Here's a patch you can try (attached).
>
> No backend API change necessary, so far.
>
> Are there many backends that could support amending?

I'm not aware of others. I think for now it's fine to support
Mercurial without an API change. Once there are more backends showing
up that should have similar support, we can generalize the approach.
Thanks!





  reply	other threads:[~2019-04-06 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 10:44 bug#34944: 27.0.50; FR: support amend in vc-hg Philipp Stephani
2019-03-22 13:18 ` Eli Zaretskii
2019-03-23  2:34   ` Richard Stallman
2019-03-23  7:28     ` Eli Zaretskii
2019-03-24  1:44       ` Richard Stallman
2019-04-03  0:33 ` Dmitry Gutov
2019-04-06 13:54   ` Philipp Stephani [this message]
2019-04-07  0:48     ` Dmitry Gutov
2019-04-17 18:40       ` Philipp Stephani
2019-04-20 21:40         ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAArVCkQz41zsa60jaZxQGWK92pPGeFLE7hVH7C42HoZDVJebuA@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=34944@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.