From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: esr@thyrsus.com, emacs-devel@gnu.org
Subject: Re: Use of "Action stamps" in commit messages
Date: Sat, 14 Jul 2018 10:08:56 +0300 [thread overview]
Message-ID: <83muuub8fr.fsf@gnu.org> (raw)
In-Reply-To: <eeb421e1-b9db-e9d4-7358-b02470a6c8a3@cs.ucla.edu> (message from Paul Eggert on Fri, 13 Jul 2018 15:10:41 -0500)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 13 Jul 2018 15:10:41 -0500
>
> Could we make it easier to generate an action stamp from the commit ID
> or from a position in a VC log buffer when editing a later commit
> message?
What UI did you have in mind? Something like "with point on a Git
SHA1 or the result of 'git describe', invoke a command that will
replace those with an action stamp"? If so, I think it would be nice
to have that, yes.
While at that: what should we do with SHA1 signatures added
automatically by the likes of "git cherry-pick -x"? Use -xe and
invoke the above hypothetical command? Something else?
next prev parent reply other threads:[~2018-07-14 7:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 9:13 Use of "Action stamps" in commit messages (WAS: [Emacs-diffs] master babe0d4: Rearrange definition of zerop in subr.el) Noam Postavsky
2018-07-13 12:01 ` Eli Zaretskii
2018-07-13 12:59 ` Use of "Action stamps" in commit messages Andy Moreton
2018-07-13 13:45 ` Eli Zaretskii
2018-07-13 15:01 ` Andy Moreton
2018-07-13 15:05 ` Eli Zaretskii
2018-07-13 17:07 ` Radon Rosborough
2018-07-13 17:24 ` Yuri Khan
2018-07-13 17:30 ` Radon Rosborough
2018-07-13 17:38 ` Eli Zaretskii
2018-07-13 17:34 ` Eli Zaretskii
2018-07-13 18:17 ` John Yates
2018-07-13 18:48 ` Eli Zaretskii
2018-07-13 15:25 ` Paul Eggert
2018-07-13 18:15 ` Eric S. Raymond
2018-07-13 18:59 ` Eli Zaretskii
2018-07-13 19:06 ` Eric S. Raymond
2018-07-13 19:30 ` Eli Zaretskii
2018-07-13 20:10 ` Paul Eggert
2018-07-13 20:47 ` Eric S. Raymond
2018-07-14 7:08 ` Eli Zaretskii [this message]
2018-07-14 14:38 ` Paul Eggert
2018-07-14 15:48 ` Eli Zaretskii
2018-07-14 9:49 ` Andy Moreton
2018-07-14 2:45 ` Noam Postavsky
2018-07-14 2:51 ` Brett Gilio
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83muuub8fr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).