unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: vc-print-log vs. bzr log
Date: Sat, 15 Sep 2012 22:36:13 +0300	[thread overview]
Message-ID: <83mx0rrscy.fsf@gnu.org> (raw)
In-Reply-To: <87wqzvb33y.fsf@rosalinde.fritz.box>

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: emacs-devel@gnu.org
> Date: Sat, 15 Sep 2012 19:36:01 +0200
> 
> > What do you see in ~/.bzr.log if you invoke
> >
> >   bzr log -l1 gnus-group.el
> >
> > from the shell prompt?  
> 
> Sat 2012-09-15 19:26:14 +0200
> 0.127  bazaar version: 2.5.1
> 0.127  bzr arguments: [u'log', u'-l1', u'gnus-group.el']
> 0.131  looking for plugins in /home/steve/.bazaar/plugins
> 0.139  looking for plugins in /usr/lib64/python2.7/site-packages/bzrlib/plugins
> 0.163  looking for plugins in /usr/lib/python2.7/site-packages/bzrlib/plugins
> 0.171  encoding stdout as sys.stdout encoding 'UTF-8'
> 0.228  opening working tree '/data/steve/bzr/emacs/quickfixes'
> 0.312  encoding stdout as sys.stdout encoding 'UTF-8'
> 18.968  Transferred: 0kB (0.0kB/s r:0kB w:0kB)
> 18.968  return code 0

So it's bzr itself, not VC.  I guess a bug report to the bzr bug
tracker is in order, after all.




  parent reply	other threads:[~2012-09-15 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15 13:07 vc-print-log vs. bzr log Stephen Berman
2012-09-15 13:37 ` Andreas Schwab
2012-09-15 14:56   ` Stephen Berman
2012-09-15 15:45     ` Eli Zaretskii
2012-09-15 16:04       ` Stephen Berman
2012-09-15 16:28         ` Eli Zaretskii
2012-09-15 17:36           ` Stephen Berman
2012-09-15 17:56             ` Andreas Schwab
2012-09-15 19:36             ` Eli Zaretskii [this message]
2012-09-15 13:51 ` Eli Zaretskii

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=83mx0rrscy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).