From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Engster <deng@randomsample.de>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: emacs-25 586b213: * lisp/url/url.el (url-retrieve-synchronously): Doc fix. (Bug#23411)
Date: Sun, 01 May 2016 19:18:45 +0200 [thread overview]
Message-ID: <874mahpuh6.fsf@gnus.org> (raw)
In-Reply-To: <8737q13dli.fsf@engster.org> (David Engster's message of "Sun, 01 May 2016 19:14:17 +0200")
David Engster <deng@randomsample.de> writes:
> Lars Ingebrigtsen writes:
>> If the latter, is there an easy way to add the string "backport:" to
>> every commit without doing it manually?
>
> FWIW, gitmerge.el should be able to detect cherry-picks through git's
> "cherry mark", so putting in an additional string to the commit message
> shouldn't be necessary. You only need to do that if you somehow modified
> the patch during cherry-picking (by resolving a conflict, for instance).
Oh, great. Then I can just do a cherry-pick -x, then, on the list of
doc fixes that apply without any conflicts. That seems to be...
uhm... 65-ish...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-05-01 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160501152515.31964.66193@vcs.savannah.gnu.org>
[not found] ` <E1awtFD-0008KC-DM@vcs.savannah.gnu.org>
2016-05-01 15:40 ` emacs-25 586b213: * lisp/url/url.el (url-retrieve-synchronously): Doc fix. (Bug#23411) Lars Ingebrigtsen
2016-05-01 15:42 ` Lars Ingebrigtsen
2016-05-01 15:45 ` Eli Zaretskii
2016-05-01 16:41 ` Lars Ingebrigtsen
2016-05-01 16:49 ` Lars Ingebrigtsen
2016-05-01 17:14 ` David Engster
2016-05-01 17:18 ` Lars Ingebrigtsen [this message]
2016-05-01 17:21 ` David Engster
2016-05-01 17:47 ` Lars Ingebrigtsen
2016-05-01 18:03 ` Eli Zaretskii
2016-05-01 18:04 ` Lars Ingebrigtsen
2016-05-01 18:15 ` Eli Zaretskii
2016-05-01 18:19 ` Lars Ingebrigtsen
2016-05-01 19:25 ` David Engster
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=874mahpuh6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).