unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Liu <sdl.web@gmail.com>
To: Daimrod <daimrod@gmail.com>
Cc: 17772-done@debbugs.gnu.org, Ryan Yeske <rcyeske@gmail.com>
Subject: bug#17772: [PATCH] Dangling channels' buffer
Date: Mon, 30 Jun 2014 10:59:32 +0800	[thread overview]
Message-ID: <m3lhsf14rv.fsf@gmail.com> (raw)
In-Reply-To: <874mzob83c.fsf@tanger.home> (daimrod@gmail.com's message of "Sat, 14 Jun 2014 10:20:07 +0900")

Version: 24.5

On 2014-06-14 10:20 +0900, Daimrod wrote:
> Here is a new patch with your proposal:

Committed and thanks,

Leo





      reply	other threads:[~2014-06-30  2:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 10:41 bug#17772: [PATCH] Dangling channels' buffer Daimrod
2014-06-13 18:36 ` Stefan Monnier
2014-06-14  1:04   ` Daimrod
2014-06-14  1:20     ` Daimrod
2014-06-30  2:59       ` Leo Liu [this message]

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=m3lhsf14rv.fsf@gmail.com \
    --to=sdl.web@gmail.com \
    --cc=17772-done@debbugs.gnu.org \
    --cc=daimrod@gmail.com \
    --cc=rcyeske@gmail.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).