From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Gnus and Emacs branches (was: [patch] gnus-agent doesn't always synchronise flags if asked to)
Date: Wed, 28 Nov 2007 21:47:02 +0100 [thread overview]
Message-ID: <v9r6iam721.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87wss3rjvz.fsf@denkblock.local>
On Tue, Nov 27 2007, Elias Oltmanns wrote:
> The ChangeLog entry is there but I fail to see the actual changes in
> gnus.el, gnus-int.el gnus-agent.el and gnus-srvr.el. Did something go
> wrong?
Obviously I didn't commit the lisp files, dunno why. Now done.
> Is there an easy way to view diffs between the trunk and the version
> included in emacs 22.x from within a gnus checkout? This way I
> could try to find out whether the same problems actually exist in
> the stable branch as well.
With CVS you can only compare branches within the same repository. In
our case you can compare v5-10 and trunk (cvs.gnus.org) e.g. with...
cvs diff -r v5-10 -r HEAD lisp/gnus.el
In Emacs, you could do...
cvs diff -r EMACS_22_BASE -r HEAD lisp/gnus/gnus.el
Note Gnus in the EMACS_22_BASE branch (5.11) is synched with v5-10
(5.10.*), Gnus trunk (No Gnus) is synched with Emacs trunk (Gnus
5.13). Note that the synching is done only semi-automatically, there
are delays (usually a couple of days, unless Miles is offline for
longer periods).
If you want to do test on the stable branch, you can checkout the
v5-10 branch by adding "-r v5-10" to the usual "cvs checkout" command.
Maybe comparing Emacs and Gnus repositories if possible using Miles'
arch repository.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2007-11-28 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 14:54 [patch] gnus-agent doesn't always synchronise flags if asked to Elias Oltmanns
2007-11-09 13:33 ` Elias Oltmanns
2007-11-24 21:51 ` Reiner Steib
2007-11-27 11:46 ` Elias Oltmanns
2007-11-28 20:47 ` Reiner Steib [this message]
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=v9r6iam721.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).