Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, ding@gnus.org, Miles Bader <miles@gnu.org>
Subject: Syncing Gnus more often?
Date: Fri, 11 Apr 2008 00:30:21 +0200	[thread overview]
Message-ID: <v9tzi9cphe.fsf@marauder.physik.uni-ulm.de> (raw)

[ I'm starting a new thread... ]

On Wed, Apr 09 2008, Stefan Monnier wrote:
[ In <news:jwvod8jhzu9.fsf-monnier+emacs@gnu.org> ]
> Maybe you want to ask Miles to do a round of sync'ing (he seems to have
> been a bit busy with other things recently).

Stefan, some time ago you offered to the arch-based sync (EMACS_22 ->
trunk) for Miles if he is too busy or offline.  If you still volunteer
to do this and it's okay for Miles, you could also sync to Gnus'
repository.  I'm sure Lars will give you write access.

I think a sufficient sync interval is once a week or so.  If it takes
much longer, chances of "forgetting" patches or conflicts tents to
increase.  Today I ran a diff Gnus trunk vs. Gnus-in-Emacs trunk and
there were much more differences (also older changes) than I expected.
I'll try to fix these after the next sync.

If the arch-based sync is sufficiently simple (i.e. documented for
someone who never used arch), I could to the Gnus sync occasionally as
well (I have access to fencepost and write access to both CVS
repositories).

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




             reply	other threads:[~2008-04-10 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 22:30 Reiner Steib [this message]
2008-04-11  1:49 ` Stefan Monnier
2008-04-13 21:04   ` Reiner Steib
2008-04-14  1:29     ` Stefan Monnier
2008-04-14  7:30       ` Reiner Steib

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=v9tzi9cphe.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).