From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
bugs@gnus.org, miles@gnu.org
Subject: Re: C-a in message.el with point between bol and :
Date: Tue, 25 Jan 2005 09:05:46 +0900 [thread overview]
Message-ID: <b9yvf9m8jad.fsf@jpl.org> (raw)
In-Reply-To: fc339e4a05012415177f25e85a@mail.gmail.com
>>>>> In <fc339e4a05012415177f25e85a@mail.gmail.com> Miles Bader wrote:
> Note that the synching is bi-directional, so if Stefan commits his
> patch to Emacs CVS, it will be propagated to the Gnus 5.10 branch and
> the Gnus trunk.
I forgot that changes in Emacs are propagated to the Gnus trunk,
not only the v5-10 branch. Thanks.
prev parent reply other threads:[~2005-01-25 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 18:59 C-a in message.el with point between bol and : Stefan Monnier
2005-01-24 22:38 ` Katsumi Yamaoka
2005-01-24 23:17 ` Miles Bader
2005-01-25 0:05 ` Katsumi Yamaoka [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=b9yvf9m8jad.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=bugs@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).