GNU bug report logs - #57807
29.0.50; Make vc-print-branch-log able to log multiple branches

Previous Next

Package: emacs;

Reported by: Sean Whitton <spwhitton <at> spwhitton.name>

Date: Wed, 14 Sep 2022 17:20:02 UTC

Severity: normal

Found in version 29.0.50

Done: Sean Whitton <spwhitton <at> spwhitton.name>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 57807 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sean Whitton <spwhitton <at> spwhitton.name>
Cc: 57807 <at> debbugs.gnu.org
Subject: Re: bug#57807: 29.0.50; Make vc-print-branch-log able to log
 multiple branches
Date: Thu, 15 Sep 2022 19:48:30 +0300
> From: Sean Whitton <spwhitton <at> spwhitton.name>
> Date: Thu, 15 Sep 2022 09:18:13 -0700
> 
> Hello,
> 
> On Thu 15 Sep 2022 at 08:33AM +03, Eli Zaretskii wrote:
> 
> > So the difference is that what you want to see is all the branches up
> > to their HEAD, and not just branches merged into the current branch,
> > is that right?
> >
> > If so, I guess some optional feature of "C-x v L" could do that.
> > However, if the repository has many branches (and ours, for example,
> > does), wouldn't that make for a crowded and hard-t-read log buffer?
> > Perhaps asking the user for a name of one branch will be enough?  More
> > than one branch could be problematic on display, I think.
> 
> Not all branches, as indeed that would quickly become unreadable.  The
> user has to say exactly which branches they would like to be included.
> And usually you wouldn't type more than two or three.

I think 3 is already too much for the largely unidimensional display
we (and Git) provide.




This bug report was last modified 2 years and 296 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.