unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 5428@debbugs.gnu.org
Subject: bug#5428: vc-annotate for Bzr does not show the date
Date: Sat, 23 Jan 2010 09:24:34 -0800 (PST)	[thread overview]
Message-ID: <201001231724.o0NHOYjb024041@godzilla.ics.uci.edu> (raw)
In-Reply-To: <jwveilhjct9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 23 Jan 2010 06:13:47 -0500")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

  > >> > Can you please explain how was this different with CVS (and all other
  > >> > VCs besides svn)?
  > >> It wasn't.  So it was a problem that wasn't solved for CVS.
  > >> Doesn't mean it should be re-introduced for Bzr.
  > > Does it mean that your personal preference should make it impossible to
  > > do useful searches by date?
  > 
  > No, just that the current preference should not simply be replaced by
  > another one, unless we provide a way to configure VC to get the current
  > preference back.

Why not first implement whatever configurability YOU want, and then
change the default display so that it does not make work harder for
other people, instead of just breaking a long time working feature?

  > FWIW, it's not impossible to do such searches: Use vc-print-log to see
  > which dates corresponds to which revision numbers, and then search by
  > revision number.

How is this better than just searching in the vc-annotate buffer that
has been the normal work flow for years?


  > > Why not fix it properly, instead of breaking it?  At least don't make it
  > > strictly worse.
  > 
  > That's exactly what I want: to fix it properly, rather than to replace
  > one problem with another.

Can you please do it in such a way that you don't replace a working (and
in use for a very long time) setup with a broken one?






  reply	other threads:[~2010-01-23 17:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  7:26 bug#5428: vc-annotate for Bzr does not show the date Dan Nicolaescu
2010-01-20 16:36 ` Chong Yidong
2010-01-20 18:18   ` Dan Nicolaescu
2010-01-20 18:19   ` Eli Zaretskii
2010-01-21 14:17 ` Stefan Monnier
2010-01-21 15:27   ` Dan Nicolaescu
2010-01-22 15:21     ` Stefan Monnier
2010-01-22 19:26       ` Dan Nicolaescu
2010-01-22 20:21         ` Eli Zaretskii
2010-01-23 11:13         ` Stefan Monnier
2010-01-23 17:24           ` Dan Nicolaescu [this message]
2019-06-27 18:13     ` Lars Ingebrigtsen
2015-05-08 21:35   ` Glenn Morris
2015-05-16 23:55     ` Dmitry Gutov
2015-05-17  1:16       ` Stefan Monnier
2015-05-17  1:30         ` Dmitry Gutov
2015-05-17  1:47         ` Dmitry Gutov
2015-05-18 16:05           ` Stefan Monnier
2016-02-28  6:14       ` Lars Ingebrigtsen
2016-02-28 18:27         ` Glenn Morris
2019-06-27 17:36           ` Lars Ingebrigtsen
2019-06-27 18:05             ` Stefan Monnier
2019-06-27 18:11               ` Lars Ingebrigtsen

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=201001231724.o0NHOYjb024041@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=5428@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).