Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Gnus 5.11 in Emacs CVS
Date: Thu, 22 Jan 2004 16:17:14 +0100	[thread overview]
Message-ID: <v9u12oko79.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m33ca8e8db.fsf@defun.localdomain>

On Thu, Jan 22 2004, Jesper Harder wrote:

>> On Thu, Jan 08 2004, Reiner Steib wrote:
[...]
>>> Naively, I would have though that it's more or less placing
>>> [gnus/]lisp files in [emacs]/lisp/gnus and [gnus/]texi in
>>> [emacs/]man.
>
> Maybe it would make sense to make a branch in Gnus cvs and start doing
> the necessary stuff, deleting files, merging from Emacs etc. there?

If we need a branch, shouldn't it be in _Emacs_ CVS to test the
integration (e.g. check that new files have to be added to CVS, ...)?
I wonder how the merge has been done last time.  I'd like to help with
it, but probably it would make more sense if someone with write access
to Emacs CVS does the first (big) step.

Maybe we should shift (or cross-post) this discussion to emacs-devel?

BTW, I've added the suggestions from your previous article [1] to my
Emacs-CVS checkout [2] and I'm using it for more than a week without
problems.

Bye, Reiner.

[1] See <news:m3u12z9klj.fsf@defun.localdomain> and
    <news:v94quywr48.fsf@marauder.physik.uni-ulm.de>.
    Not addressed yet: byte-compiler warnings

[2] The updated shell script is available here:
    <URL:http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/gnus/Gnus-5-11.sh>
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2004-01-22 15:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 11:01 Per Abrahamsen
2004-01-05 21:18 ` Steve Youngs
2004-01-05 22:01   ` Reiner Steib
2004-01-06  5:08     ` Lars Magne Ingebrigtsen
2004-01-08 17:58       ` Reiner Steib
2004-01-13 22:22         ` Reiner Steib
2004-01-13 23:08           ` Jesper Harder
2004-01-14  5:15           ` Jesper Harder
2004-01-14  6:20             ` Simon Josefsson
2004-01-15  0:46               ` Jesper Harder
2004-01-15  2:30                 ` Simon Josefsson
2004-01-14 14:18             ` Reiner Steib
2004-01-22  7:43           ` Jesper Harder
2004-01-22 15:17             ` Reiner Steib [this message]
2004-02-15  0:03               ` Miles Bader
2004-02-15  0:18                 ` Miles Bader
2004-04-14 20:24                 ` Reiner Steib
2004-04-15  0:37                   ` Miles Bader
2004-05-12 10:17                     ` Reiner Steib
2004-01-05 22:12   ` Xavier Maillard
2004-01-06 13:46   ` Per Abrahamsen

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=v9u12oko79.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).