From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Dynamic rescaling in doc-view.el
Date: Thu, 06 Jan 2011 05:56:24 +0200 [thread overview]
Message-ID: <83bp3un0rb.fsf@gnu.org> (raw)
In-Reply-To: <87vd23m373.fsf@member.fsf.org>
> From: Tassilo Horn <tassilo@member.fsf.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 05 Jan 2011 22:49:04 +0100
>
> >> % bzr commit
> >> Unable to obtain lock chroot-3070208716:///emacs/trunk/.bzr/branch/lock
> >> held by tsdh@vcs-noshell on host vcs-noshell [process #27158]
> >> locked 4 minutes, 25 seconds ago
> >> Will continue to try until 21:23:04, unless you press Ctrl-C
> >> If you're sure that it's not being modified, use bzr break-lock chroot-3070208716:///emacs/trunk/.bzr/branch/lock
> >> bzr: ERROR: Could not acquire lock "(remote lock)":
> >> bzr+ssh://tsdh@bzr.savannah.gnu.org/emacs/
> >>
> >> Could someone confirm that the commit arrived upstreams?
> >
> > If bzr failed to acquire the lock, your commit didn't arrive upstream.
> > Try later, and if the problem persists, break the lock.
>
> But how do I do (from my bound branch)?
It tells you in the message: "bzr break-lock".
> bzr stat shows no changes, and bzr log shows my commit...
That's expected, since bzr commits locally before pushing upstream.
next prev parent reply other threads:[~2011-01-06 3:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 21:27 Dynamic rescaling in doc-view.el Tassilo Horn
2011-01-05 21:35 ` Eli Zaretskii
2011-01-05 21:49 ` Tassilo Horn
2011-01-05 22:13 ` Tassilo Horn
2011-01-06 4:01 ` Eli Zaretskii
2011-01-06 5:15 ` Glenn Morris
2011-01-06 7:08 ` Tassilo Horn
2011-01-06 7:57 ` Glenn Morris
2011-01-06 9:25 ` Eli Zaretskii
2011-01-06 3:56 ` Eli Zaretskii [this message]
2011-01-07 3:52 ` Stefan Monnier
2011-01-07 7:45 ` Eli Zaretskii
2011-01-05 21:38 ` Andreas Schwab
2011-01-06 3:18 ` joakim
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=83bp3un0rb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tassilo@member.fsf.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).