Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Sync of Gnus with Emacs
Date: 23 Aug 2004 12:04:31 -0400	[thread overview]
Message-ID: <4nvff9lu28.fsf@lifelogs.com> (raw)
In-Reply-To: <v9eklyke6b.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 23 Aug 2004 00:20:44 +0200")

On Mon, 23 Aug 2004, 4.uce.03.r.s@nurfuerspam.de wrote:

> I'd like to ask all Gnus developers to apply bug fixes and doc
> fixes[1] that went into the trunk (No Gnus) also in the v5-10 branch.
> I will merge those changes into the branch "gnus-5_10-branch" of Emacs
> then.  If you have write access for Emacs, you can apply there
> yourself, of course.

You mean that each developer should apply his own fixes to the 5-10
branch?  Some developers are busy and can't do this - should we build
a list of commits, sorted by name and date?  This may depend on an
unresponsive (for whatever reason) developer - we need to either
assign the task to someone else or forget about those fixes.

Ted



  parent reply	other threads:[~2004-08-23 16:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 22:20 Reiner Steib
2004-08-22 22:33 ` Simon Josefsson
2004-08-23  8:33   ` Reiner Steib
2004-08-23  8:59     ` Simon Josefsson
2004-08-23 16:04 ` Ted Zlatanov [this message]
2004-08-24 15:49   ` Reiner Steib
2004-08-25  0:32     ` Katsumi Yamaoka
2004-08-25  8:35       ` Reiner Steib
2004-08-25  9:26         ` Katsumi Yamaoka
2004-08-26 10:00           ` Katsumi Yamaoka
2004-09-09 23:38       ` Miles Bader
2004-09-10  0:15         ` Katsumi Yamaoka
2004-08-31 15:58     ` Reiner Steib
2004-09-01 14:50     ` Simon Josefsson
2004-09-01 16:04       ` Reiner Steib
2004-09-01 20:20         ` Simon Josefsson
2004-09-01 23:03         ` Miles Bader
2004-09-03  7:37       ` Katsumi Yamaoka
2004-09-07 19:38     ` Ted Zlatanov
2004-09-08 18:20       ` Reiner Steib
2004-09-10 17:59         ` Ted Zlatanov
2004-09-11 15:08           ` Reiner Steib
2004-10-19  3:58     ` Kevin Greiner

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=4nvff9lu28.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).