From: Dan Nicolaescu <dann@ics.uci.edu>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: 618@debbugs.gnu.org
Subject: bug#618: 23.0.60; Bazaar support: no revision number with lightweight checkouts
Date: Tue, 5 Jan 2010 13:22:35 -0800 (PST) [thread overview]
Message-ID: <201001052122.o05LMZAn015668@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87aaws6hzz.fsf@physik.rwth-aachen.de> (Torsten Bronger's message of "Tue, 05 Jan 2010 10:03:28 +0100")
Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
> Hallöchen!
>
> Chong Yidong writes:
>
> > Hi Torsten,
> >
> >> In Bazaar lightweight checkouts, Emacs doesn't show the revision
> >> number in the mode line.
> >
> > I think this depends on the branch format, whose default has
> > changed since this bug was first reported. For the latest version
> > of bzr, Emacs shows the revision number in the mode line for
> > lightweight checkouts (at least for me).
>
> If I remember correctly, someone fixed this shortly after my report.
> However, we "agreed" on a rather poor solution: Falling back to
> calling "bzr revno" for every open file. I've used this solution
> for many months now. It slows down Emacs' startup time
> significantly. After all, bzr being a Python program, causes a lot
> of overhead.
>
> Therefore, on the long run, Emacs should use the file system even
> for lightweight checkouts. (As long as the branch is local of
> course. But this is typical usage lightweight checkouts.)
I checked in a fix, bzr should not be run anymore for lightweight checkouts.
next prev parent reply other threads:[~2010-01-05 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 22:43 bug#618: 23.0.60; Bazaar support: no revision number with lightweight checkouts Chong Yidong
2010-01-02 7:00 ` Dan Nicolaescu
2010-01-02 21:21 ` Chong Yidong
2010-01-05 9:03 ` Torsten Bronger
2010-01-05 21:22 ` Dan Nicolaescu [this message]
2010-01-05 22:38 ` Torsten Bronger
-- strict thread matches above, loose matches on Subject: below --
2008-07-27 20:41 Torsten Bronger
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=201001052122.o05LMZAn015668@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=618@debbugs.gnu.org \
--cc=bronger@physik.rwth-aachen.de \
/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.