unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vladimir Kazanov <vekazanov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: The overlay branch (yet again)
Date: Fri, 6 Dec 2019 06:48:02 +0000	[thread overview]
Message-ID: <CAAs=0-2KNZZB_rxxhy5StREX_XCC32jTTpndLcaJrcH7DgxwEg@mail.gmail.com> (raw)
In-Reply-To: <8336dyiv7q.fsf@gnu.org>

On Thu, Dec 5, 2019 at 4:38 PM Eli Zaretskii <eliz@gnu.org> wrote:
> It would, but how would you produce such a patch if there's a single
> commit on the branch, which mixes these changes with others?

I wouldn't, at least not this time. But I already have a second patch
in the works, and I really want it to be usable the way I send it..

Stefan already merged the patch, by the way. Nice!


--
Yours sincerely,


Vladimir Kazanov


--
С уважением,

Владимир Казанов



  reply	other threads:[~2019-12-06  6:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 14:44 The overlay branch (yet again) Vladimir Kazanov
2019-12-03 15:35 ` Vladimir Kazanov
2019-12-03 15:58   ` Eli Zaretskii
2019-12-03 16:06   ` martin rudalics
2019-12-03 16:21     ` Vladimir Kazanov
2019-12-03 17:58       ` Stefan Monnier
2019-12-03 20:46         ` Vladimir Kazanov
2019-12-03 22:43           ` Stefan Monnier
2019-12-04 11:41             ` Vladimir Kazanov
2019-12-05 14:13               ` Vladimir Kazanov
2019-12-05 15:14                 ` Eli Zaretskii
2019-12-05 15:31                   ` Vladimir Kazanov
2019-12-05 16:38                     ` Eli Zaretskii
2019-12-06  6:48                       ` Vladimir Kazanov [this message]
2019-12-09  8:10                         ` Vladimir Kazanov

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='CAAs=0-2KNZZB_rxxhy5StREX_XCC32jTTpndLcaJrcH7DgxwEg@mail.gmail.com' \
    --to=vekazanov@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rudalics@gmx.at \
    /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).