all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Dynamic rescaling in doc-view.el
Date: Wed, 05 Jan 2011 22:49:04 +0100	[thread overview]
Message-ID: <87vd23m373.fsf@member.fsf.org> (raw)
In-Reply-To: <83ei8rm3tr.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Jan 2011 23:35:28 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Tassilo Horn <tassilo@member.fsf.org>
>> Date: Wed, 05 Jan 2011 22:27:12 +0100
>> 
>> When committing, I had some bzr problems:
>> 
>> % 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)?  bzr stat shows no changes, and
bzr log shows my commit...

Bye,
Tassilo



  reply	other threads:[~2011-01-05 21:49 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vd23m373.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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.