Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Ding List <ding@gnus.org>, Emacs development <emacs-devel@gnu.org>
Subject: Re: merge emacs Gnus changes (was: nndb.el requires tcp)
Date: Thu, 16 Sep 2004 09:45:45 -0400	[thread overview]
Message-ID: <20040916134545.GB300@fencepost> (raw)
In-Reply-To: <20040916133826.GA300@fencepost>

On Thu, Sep 16, 2004 at 09:38:26AM -0400, Miles Bader wrote:
> > 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).

BTW I _can_ do such merges, but there should be some guideline.

-Miles
-- 
My spirit felt washed.  With blood.  [Eli Shin, on "The Passion of the Christ"]



  reply	other threads:[~2004-09-16 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01c49720$Blat.v2.2.2$b48fff20@zahav.net.il>
     [not found] ` <iluu0u6e6tx.fsf@latte.josefsson.org>
     [not found]   ` <01c49729$Blat.v2.2.2$ea11b9a0@zahav.net.il>
     [not found]     ` <iluisame436.fsf@latte.josefsson.org>
     [not found]       ` <v9vfem5mer.fsf@marauder.physik.uni-ulm.de>
     [not found]         ` <ilur7paclxh.fsf@latte.josefsson.org>
     [not found]           ` <20040910140108.GA16207@fencepost>
2004-09-16 13:27             ` Reiner Steib
2004-09-16 13:38               ` Miles Bader
2004-09-16 13:45                 ` Miles Bader [this message]
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 22:49                         ` Miles Bader
2004-09-19 21:00                       ` Miles Bader

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=20040916134545.GB300@fencepost \
    --to=miles@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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.
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).