From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Get rid of cut buffer code, any objections?
Date: Thu, 02 Sep 2010 12:25:31 +0200 [thread overview]
Message-ID: <4C7F7B9B.3070407@swipnet.se> (raw)
In-Reply-To: <87vd6tyshq.fsf@stupidchicken.com>
2010-08-30 00:16, Chong Yidong skrev:
> Jan Djärv<jan.h.d@swipnet.se> writes:
>
>> I have started to remove cut-buffer support for X11 (nothing checked
>> in sofar). Are there any objections?
>
> Go for it. Don't forget NEWS.
Done. I did forget NEWS and documentation, so there where multiple commits.
Jan D.
next prev parent reply other threads:[~2010-09-02 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 17:24 Get rid of cut buffer code, any objections? Jan Djärv
2010-08-29 19:54 ` Miles Bader
2010-08-30 5:47 ` Jan Djärv
2010-08-29 22:16 ` Chong Yidong
2010-09-02 10:25 ` Jan Djärv [this message]
2010-09-02 16:02 ` Chong Yidong
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=4C7F7B9B.3070407@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=cyd@stupidchicken.com \
--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).