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, 31 Aug 2004 17:58:31 +0200	[thread overview]
Message-ID: <v98ybv7108.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v9eklwy1s7.fsf@marauder.physik.uni-ulm.de>

On Tue, Aug 24 2004, Reiner Steib wrote:

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

Because cvs unable to show diffs on a branch, we should generously add
tags before and after merging:

- Update and tag the v5-10 branch with a pre-merge tag:

  cd /path/to/v5-10
  cvs update
  cvs tag "gnus-5_10-pre-merge-whatever"

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

According to RMS' advice, I changed the ChangeLog dates to the date of
the installation of the change in the respective branch.  The dates in
the ChangeLog file should be monotonic.

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

- Tag the v5-10 branch with a post-merge tag:

  cd /path/to/v5-10
  cvs tag "gnus-5_10-post-merge-whatever"


In this way, we can create whatever.patch using...

  cvs diff -r "gnus-5_10-pre-merge-whatever" \
    -r "gnus-5_10-post-merge-whatever" > whatever.patch

... and apply it in Emacs' repository.

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

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




  parent reply	other threads:[~2004-08-31 15:58 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
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 [this message]
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=v98ybv7108.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).