Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Sync of Gnus with Emacs
Date: Tue, 24 Aug 2004 17:49:12 +0200	[thread overview]
Message-ID: <v9eklwy1s7.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nvff9lu28.fsf@lifelogs.com>

On Mon, Aug 23 2004, Ted Zlatanov wrote:

> 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?  

Basically yes.  It's more time consuming for someone else to find out
whether the change is relevant for v5-10 and how to redo the change in
v5-10 in case of failed hunks from `patch'.  Because only doc- and
bugfixes should go there, the number of relevant changes should be
quite small.

Here is a suggestion on how to do it rather convenient (suggestions
for improvement very welcome):

- Open the ChangeLog file in the No Gnus directory.

- Goto 2004-01-04 (No Gnus starts here).  Search for your name with
  `C-r'.

- (If the entry might be relevant:) 
  Open the source file(s) *in the v5-10* directory, browse the log
  with `C-x v l', use `d' (log-view-diff) to view the change.

  If relevant, apply the hunk(s) using `C-c C-a' from the *vc-diff*
  buffer.  Add the ChangeLog entry using the current date.  Commit.

- Do this for the ChangeLogs in texi/ and lisp/.

- Post a message in this thread that you have checked (and installed)
  your changes.

> Some developers are busy and can't do this - should we build a list
> of commits, sorted by name and date?  

I think that the ChangeLogs are sufficient.

> 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.

Of course everyone can also apply changes from someone else.

Does this answer your questions?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2004-08-24 15:49 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
2004-08-24 15:49   ` Reiner Steib [this message]
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=v9eklwy1s7.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=Reiner.Steib@gmx.de \
    /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).