all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: deng@randomsample.de, 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 20:04:54 +0200	[thread overview]
Message-ID: <87fuu1zmbd.fsf@gnus.org> (raw)
In-Reply-To: <83mvo9mz9z.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 01 May 2016 21:03:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Ok; I've now done the cherry-pick on all 65 doc fixes, and the result is
>> without conflicts, and emacs-25 still builds.  :-)
>
> Thanks.
>
>> I just wanted to triple-check before pushing: Is this the way to do it?
>
> What is "this" that you are asking about?

Uhm...  cherry-picking and pushing?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2016-05-01 18:04 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
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 [this message]
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=87fuu1zmbd.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 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.