Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Miles Bader <miles@gnu.org>,
	Romain Francoise <romain@orebokech.com>,
	Didier Verna <didier@xemacs.org>
Subject: Reminder: bug fixes should be applied to v5-10 (was: vacation)
Date: Sat, 06 Aug 2005 17:33:45 +0200	[thread overview]
Message-ID: <v9oe8b84h2.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <buoacjwkbrm.fsf@mctpc71.ucom.lsi.nec.co.jp> (Miles Bader's message of "Fri, 05 Aug 2005 17:50:53 +0900")

On Fri, Aug 05 2005, Miles Bader wrote:

> I'll be leaving on 3-week vacation from monday, so won't be doing my
> usual gnus-emacs syncing until I return.

Thanks a lot for your work, Miles.

I'd like to remind the Gnus developers that bug fixes--this includes
fixed typos, doc additions, etc.--should eventually go to the stable
branch v5-10 (to be released as Gnus 5.10.7 someday) as well.  Of
course this doesn't apply to stuff that is new in No Gnus.

You can either apply bug fixes to the trunk *and* the v5-10 branch, or
apply the only to v5-10 (Miles will sync those changes to the trunk
from time to time).

Emacs developers (without write access to Gnus' repository) can commit
bug fixes to Gnus in Emacs' repository.  Miles will sync those changes
to Gnus v5-10 branch and to the trunk.  (Gnus 5.11 in Emacs 22
virtually is the same as v5-10.)

Bye, Reiner.

[ CC-ing Romain and Didier, because I suspect that some of your recent
changes should also be applied to v5-10. ]
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2005-08-06 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  8:50 vacation Miles Bader
2005-08-06 15:33 ` Reiner Steib [this message]
2005-08-06 17:21   ` Reminder: bug fixes should be applied to v5-10 Romain Francoise
2005-08-09 16:20   ` Jesper Harder
2005-08-26 22:23     ` Miles Bader
2005-08-28 13:33       ` Reiner Steib

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=v9oe8b84h2.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=didier@xemacs.org \
    --cc=miles@gnu.org \
    --cc=romain@orebokech.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.
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 NNTP newsgroup(s).