Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Small docstring bug in `gnus-treat-display-face'
Date: Mon, 05 Jan 2009 22:07:22 +0100	[thread overview]
Message-ID: <877i59sbqt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <871vvhkd7g.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Mon, 05 Jan 2009 16:02:59 +0100")

On Mon, Jan 05 2009, Tassilo Horn wrote:

> I'd fix it on my own, but I'm not sure how to do that best.  I don't
> have the Gnus repository checked out and use Emacs 23 from CVS with the
> bundled Gnus version.  Would it be ok to fix it in Emacs CVS, both in
> HEAD and EMACS_22 branch?  And if yes, would I make the changes manually
> in each branch or only in one and merge it to the other one?  

Just commit it to Emacs trunk.

Previously such changes should have been made only in one of the
stable branches (Gnus v5-10 branch or Emacs_22).  (Additionally adding
it to the trunk was fine as well.)

But now, the Emacs 22 branch has been retired, AFAIK.  We will do a
final 5.10.* release from v5-10, 5.10.12, soon.  Thereafter we will
retire the v5-10 branch as well (we could still use it for in case of
an emergency release, e.g. security fix).

> Does CVS have merge support anyway?

Quite limited.  But synching is done semi-automatically by Miles Bader
via Arch.  See emacs/doc/misc/gnus-coding.texi or
gnus/texi/gnus-coding.texi (not yet updated for the post-Emacs-22 /
post-Gnus-5.10 time).

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



  reply	other threads:[~2009-01-05 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 15:02 Tassilo Horn
2009-01-05 21:07 ` Reiner Steib [this message]
2009-01-06 11:30   ` Tassilo Horn

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=877i59sbqt.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.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).