unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	Stefan Monnier <monnier@IRO.UMontreal.CA>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Relationship between 23.1.90 pretest and 23.2 pretest?
Date: Sun, 13 Dec 2009 19:10:00 -0500	[thread overview]
Message-ID: <87fx7ev2jr.fsf@red-bean.com> (raw)
In-Reply-To: <655B1275-93C1-4DB3-A016-55AC61A1E384@swipnet.se> ("Jan Djärv"'s message of "Sun, 13 Dec 2009 01:36:42 +0100")

Jan Djärv <jan.h.d@swipnet.se> writes:
> I haven't read this thread. Did we just move to Bzr?  I missed the
> announcement.

We are moving now.  

The first step is to make the CVS repository read-only.  Then Andreas
can do a clean final conversion, without worrying about, say, a
non-atomic multi-directory CVS commit being only partially included in
the conversion.

Thus there will be a brief period, while Andreas converts, when we can't
make commits to CVS but Bzr is not ready either.  It shouldn't be long;
I don't know exactly how long these conversions take, but my guess is a
day or less.  You can continue to commit to CVS until the repository
goes read-only, of course.

(I suppose there's an outside chance of a race condition, due to CVS's
non-atomicity, whereby some of a given commit gets in but not all,
because the admins make the repository read-only during the commit.  In
practice, I'm not worried about it.  There are ways they could avoid
even that small risk... but it's better just to let them do whatever is
easiest for them, so that it gets done sooner.)

-Karl

> 12 dec 2009 kl. 22.09 skrev Karl Fogel <kfogel@red-bean.com>:
>> Chong Yidong <cyd@stupidchicken.com> writes:
>>> Karl Fogel <kfogel@red-bean.com> writes:
>>>> Shall I file an SR now, asking the admins to make the CVS repository
>>>> read-only?  I don't see one already -- but I don't want to step on
>>>> anyone's toes if one of you have already put in the request.
>>>
>>> Please do.
>>
>> https://savannah.gnu.org/support/index.php?107170




  reply	other threads:[~2009-12-14  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 14:31 Relationship between 23.1.90 pretest and 23.2 pretest? Karl Fogel
2009-12-10 15:40 ` Chong Yidong
2009-12-10 17:05   ` Stefan Monnier
2009-12-10 23:39     ` Juanma Barranquero
2009-12-11  8:27       ` Eli Zaretskii
2009-12-11 16:57     ` Chong Yidong
2009-12-12  4:42       ` Stefan Monnier
2009-12-12 20:52         ` Karl Fogel
2009-12-12 20:56           ` Chong Yidong
2009-12-12 21:09             ` Karl Fogel
2009-12-13  0:36               ` Jan Djärv
2009-12-14  0:10                 ` Karl Fogel [this message]
2009-12-15 22:59               ` Bazaar switchover: waiting for admins, how to speed it? Karl Fogel

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=87fx7ev2jr.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --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.
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).