From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [emacs-diffs-request@gnu.org: Emacs-diffs Digest, Vol 96, Issue 98]
Date: Tue, 30 Nov 2010 13:49:06 -0500 [thread overview]
Message-ID: <874oaytzod.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwv62vesmhm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 30 Nov 2010 13:21:50 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> I have checkouts of both the trunk and emacs-23 taken minutes before
>> savannah went down: revisions 102543 and 100249 respectively. (Savannah
>> went down just as I was committing to the trunk, and for a minute I
>> thought my commit had somehow crashed *.gnu.org).
>
>> So, a simple "bzr push" from the bound branches should do the trick?
>
> All that matters is that noone commits until the latest commit has
> been pushed back onto savannah. So, I'd urge everyone to try
> "update/pull" first, then "push", and then wait for a day (or two)
> before committing, in case someone else already has a more recent
> version of the branch.
Looks like bzr.savannah.gnu.org is back up. I've pushed emacs-23 and
trunk.
In the case of the trunk, I'm almost completely certain that I have the
latest copy, since, as I said, Savannah went down just as (or a minute
after) I did my last commit.
next prev parent reply other threads:[~2010-11-30 18:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 15:44 [emacs-diffs-request@gnu.org: Emacs-diffs Digest, Vol 96, Issue 98] Eli Zaretskii
2010-11-28 18:09 ` Andreas Schwab
2010-11-28 19:02 ` Glenn Morris
2010-11-29 6:40 ` Glenn Morris
2010-11-29 18:07 ` Stefan Monnier
2010-11-29 19:08 ` Eli Zaretskii
2010-11-29 20:09 ` Glenn Morris
2010-11-29 20:54 ` Eli Zaretskii
2010-11-29 21:07 ` Andreas Schwab
2010-11-30 1:56 ` Chong Yidong
2010-11-30 3:59 ` Eli Zaretskii
2010-11-30 18:21 ` Stefan Monnier
2010-11-30 18:49 ` Chong Yidong [this message]
2010-11-30 18:28 ` Andreas Schwab
2010-11-30 16:52 ` Sean Sieger
2010-12-01 8:43 ` Andreas Schwab
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=874oaytzod.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.