unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Syncing Gnus more often?
Date: Sun, 13 Apr 2008 21:29:22 -0400	[thread overview]
Message-ID: <jwv63ulp6x0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <v98wzh31qs.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 13 Apr 2008 23:04:43 +0200")

>>> 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 don't think moving the single point of failure from here to there
>> won't help much, really (unless Miles is indeed too busy, of course).
>> What I'd like is to make it possible for various people to do it.

> If Miles, you and me could do it, it won't be a single point of
> failure anymore.

Indeed, but IIUC the current setup used by Miles keeps the mapping
between CVS and Arch locally on Miles's machine, so I believe that the
scripts need to be changed/improved to allow multiple people to do
the syncs.

>> Or otherwise make it 100% automatic.  E.g. if there are conflicts, just
>> commit the resulting tree (with its conflicts) and suspend sync'ing until
>> some commits a new tree without conflicts.
> Maybe this could work.

But again requires changes to the scripts.
Miles, can you help out?


        Stefan




  reply	other threads:[~2008-04-14  1:29 UTC|newest]

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

  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=jwv63ulp6x0.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=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).