unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: Re: Switching to bzr: what remains to be done?
Date: Mon, 08 Dec 2008 16:44:57 -0500	[thread overview]
Message-ID: <jwvk5aaz6wz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200812081929.mB8JTVZQ017980@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Mon, 8 Dec 2008 11:29:31 -0800 (PST)")

> Plese convey to the bzr developers that the "log" command could use some
> improvements:
> 1. it only takes a single file as argument
> 2. bzr log SUBDIR 
> does not seem to DTRT, it should show the logs for all things in that
> subdir, instead it seems to show only one entry

There's a long standing Trac ticket for that.  There doesn't seem to be
much interest in fixing it, somehow.  The Trac ticket is
https://bugs.launchpad.net/bzr/+bug/211852 and I see that
I misunderstood at that point thinking that "SUBDIR" worked whereas it
indeed doesn't (basically it only gives info about the changes to the
dir itself, i.e. when it was created and maybe when it was moved or when
its access rights were changed).
I'm pretty sure I saw a bug report about that at some point but can't
find it now.  Feel free to look for it and add your voice to it, or file
a new one.

> Also the headers for "diff" should show the versions, if you do a C-x v =
> for 2 random versions, then save that buffer, there's no way to see what
> versions the diff came from.  IMHO this is crucial to have.

The corresponding Trac ticket is https://bugs.launchpad.net/bzr/+bug/130588.
Making noise there can't hurt.


        Stefan




  parent reply	other threads:[~2008-12-08 21:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 18:59 Switching to bzr: what remains to be done? Karl Fogel
2008-12-08 19:29 ` Dan Nicolaescu
2008-12-08 19:51   ` Karl Fogel
2008-12-08 21:44   ` Stefan Monnier [this message]
2008-12-11 22:43     ` Karl Fogel
2008-12-08 19:54 ` Stefan Monnier
2008-12-09  0:59   ` Stephen J. Turnbull
     [not found]     ` <878wqqf8gr.fsf@notengoamigos.org>
2008-12-09  3:16       ` Stefan Monnier
     [not found]   ` <87hc5ef9mf.fsf@notengoamigos.org>
2008-12-09  3:32     ` Stefan Monnier
2008-12-09  9:33       ` Andreas Schwab
     [not found]       ` <87zlj5dvij.fsf@notengoamigos.org>
2008-12-09 19:55         ` Stefan Monnier
2008-12-09  2:45 ` Dan Nicolaescu
2008-12-11 20:23   ` Karl Fogel
2008-12-17 22:59     ` Karl Fogel
2008-12-18  8:00       ` Tassilo Horn
2008-12-18 16:28         ` Karl Fogel
2008-12-19  8:22           ` Tassilo Horn
2008-12-19  8:29         ` Giorgos Keramidas
2008-12-18 20:26       ` Dan Nicolaescu
2009-01-05  0:00       ` Tom Tromey
2009-01-05  2:14         ` Stefan Monnier
2009-01-05  2:42           ` Tom Tromey
2009-01-05  4:04             ` Stefan Monnier
2009-01-06  0:01             ` Richard M Stallman
  -- strict thread matches above, loose matches on Subject: below --
2008-12-08 16:32 Karl Fogel

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=jwvk5aaz6wz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).