all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
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:14:17 +0200	[thread overview]
Message-ID: <8737q13dli.fsf@engster.org> (raw)
In-Reply-To: <87a8k9pvtb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 01 May 2016 18:49:52 +0200")

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).

-David



  reply	other threads:[~2016-05-01 17:14 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 [this message]
2016-05-01 17:18             ` Lars Ingebrigtsen
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

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

  git send-email \
    --in-reply-to=8737q13dli.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 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.