From: Miles Bader <miles@gnu.org>
Subject: Re: merge emacs Gnus changes (was: nndb.el requires tcp)
Date: Thu, 16 Sep 2004 09:38:26 -0400 [thread overview]
Message-ID: <20040916133826.GA300@fencepost> (raw)
In-Reply-To: <v9hdpytkd0.fsf@marauder.physik.uni-ulm.de>
On Thu, Sep 16, 2004 at 03:27:07PM +0200, Reiner Steib wrote:
> > It's slightly easier for me if changes are installed on the Gnus v5-10
> > branch, from where I can propagate them to Emacs CVS.
>
> Did/will you also propagate changes from the v5-10 branch to the trunk
> in Gnus' CVS? Or should the Gnus developers install those changes
> manually in the v5-10 branch _and_ on the trunk?
My assumption (so far) is that all fixes on the v5-10 branch are already on
the trunk in some form (often a modified form of course).
-Miles
--
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over. --Ian Wolff
next prev parent reply other threads:[~2004-09-16 13:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 10:25 nndb.el requires tcp Eli Zaretskii
2004-09-10 10:50 ` Simon Josefsson
2004-09-10 11:31 ` Eli Zaretskii
2004-09-10 11:49 ` Simon Josefsson
2004-09-10 12:38 ` Reiner Steib
2004-09-10 13:07 ` Simon Josefsson
2004-09-10 14:01 ` Miles Bader
2004-09-16 13:27 ` merge emacs Gnus changes (was: nndb.el requires tcp) Reiner Steib
2004-09-16 13:38 ` Miles Bader [this message]
2004-09-16 13:45 ` Miles Bader
2004-09-18 13:16 ` Miles Bader
2004-09-19 19:40 ` merge emacs Gnus changes Reiner Steib
2004-09-19 20:43 ` Reiner Steib
2004-09-19 21:00 ` Miles Bader
2004-09-10 14:12 ` [Gnus] @copying in {pgg,sieve}.texi; FLIM files (was: nndb.el requires tcp) Reiner Steib
2004-09-17 9:05 ` nndb.el requires tcp Kai Grossjohann
2004-09-17 13:25 ` Lars Magne Ingebrigtsen
2004-09-18 19:07 ` Richard Stallman
2004-09-18 20:13 ` Lars Magne Ingebrigtsen
2004-09-20 0:05 ` Richard Stallman
2004-09-20 7:59 ` Kai Grossjohann
2004-09-17 23:21 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040916133826.GA300@fencepost \
--to=miles@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).