From: Miles Bader <miles@gnu.org>
Cc: Hoey@aic.nrl.navy.mil, emacs-devel@gnu.org,
Richard Stallman <rms@gnu.org>, Miles Bader <miles@gnu.org>
Subject: Re: What shall we do to verify the CVS diffs for emacs?
Date: Fri, 16 Jan 2004 20:27:35 -0500 [thread overview]
Message-ID: <20040117012735.GA23748@fencepost> (raw)
In-Reply-To: <m3zncnfie3.fsf@kfs-l.imdomain.dk>
On Sat, Jan 17, 2004 at 02:55:48AM +0100, Kim F. Storm wrote:
> I don't recall, so is the arch archive just a mirror of CVS, or
> is it two ways (i.e. will changes to arch propagates back to CVS) ?
It's two-way.
> If the latter is the case, who has access to your arch archive,
> and how do you control that access?
It's my archive, so of course I control what goes into it (the same way you'd
control any files on unix). Inter-archive merging in arch is usually `pull'
based, so if I wanted to merge changes from someone elses branch, I'd have to
explicitly do so -- in a way it's similar to applying patches someone sends
to the mailing list, just more convenient and with better record-keeping.
The remote mirrors on non-GNU machines, OTOH, _are_ just mirrors; of course
now that everything's signed I'd have no qualms about using them to restore
the master fencepost copy if something horrible happened.
-Miles
--
If you can't beat them, arrange to have them beaten. [George Carlin]
next prev parent reply other threads:[~2004-01-17 1:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 21:34 What shall we do to verify the CVS diffs for emacs? Dan Hoey
2004-01-14 6:14 ` Eli Zaretskii
2004-01-14 20:08 ` Dan Hoey
2004-01-15 11:43 ` Thien-Thi Nguyen
2004-01-15 18:47 ` David Kastrup
2004-01-15 20:32 ` Thien-Thi Nguyen
2004-01-15 21:21 ` Richard Stallman
2004-01-16 2:11 ` Kim F. Storm
2004-01-16 19:54 ` Richard Stallman
2004-01-16 23:04 ` Miles Bader
2004-01-17 1:55 ` Kim F. Storm
2004-01-17 1:27 ` Miles Bader [this message]
2004-01-17 12:54 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 1:29 Kim F. Storm
2003-12-17 3:27 ` Richard Stallman
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=20040117012735.GA23748@fencepost \
--to=miles@gnu.org \
--cc=Hoey@aic.nrl.navy.mil \
--cc=emacs-devel@gnu.org \
--cc=rms@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).