all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 57807@debbugs.gnu.org
Subject: bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches
Date: Wed, 14 Sep 2022 22:17:13 +0300	[thread overview]
Message-ID: <86v8ppn5b2.fsf@mail.linkov.net> (raw)
In-Reply-To: <87czbxub4b.fsf@melete.silentflame.com> (Sean Whitton's message of "Wed, 14 Sep 2022 10:19:48 -0700")

> vc-git-log-edit-mode is already able to properly understand git-log(1)

I suppose vc-git-log-view-mode, not vc-git-log-edit-mode?

> output which logs multiple branches.  Here's a hack to demonstrate that:
>
>     (let ((default-directory "~/src/emacs/")
>           (vc-git-log-switches
>            (cons "origin/scratch/posix-spawn" vc-git-log-switches)))
>       (call-process-shell-command "git branch -f tmp 4b2ca6bfc0")
>       (vc-print-branch-log "tmp"))
>
> (4b2ca6bfc0 is an old tip of master close to scratch/posix-spawn.)

Is this equivalent to `M-& git log origin/scratch/posix-spawn 4b2ca6bfc0`,
then enabling vc-git-log-view-mode in the output buffer?

> An example of a case in which it is useful to produce logs like this is
> when you're trying to figure out how several feature branches relate to
> each other and to the trunk.

I never encountered anything like this.  I wonder if this is a common need?

> I don't think the idea of producing a log showing more than one branch
> at once is fundamentally git-specific.  So I would like to extend
> vc-print-branch-log to allow logging more than one branch, or
> alternatively, add a vc-print-branch-logs command.

Maybe vc-print-branch-logs, to keep the original vc-print-branch-log
uncomplicated.

> I believe that there are two design issues, on which I'm requesting
> review/input:
>
> (1) Extending the VC history functions API to permit expressing a
> request for the backend to print a log of multiple branches.  We could
> allow the START-REVISION argument to `print-log' to take a list of
> branches, or add an additional optional argument
> ADDITIONAL-START-REVISIONS.  The latter seems more robust to me.
>
> (2) How could vc-print-branch-log prompt the user for multiple branch
> names?  Magit has the user separate branch names with commas, offering
> completion for each branch name.  But I suppose commas never appearing
> in branch names is git-specific.  So the command could prompt the user
> repeatedly for branch names, until the user hits RET to input a
> zero-length branch name, indicating they've input them all.

Maybe by using completing-read-multiple with branch names separated
by crm-separator, not necessarily comma?





  parent reply	other threads:[~2022-09-14 19:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 17:19 bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches Sean Whitton
2022-09-14 17:41 ` Eli Zaretskii
2022-09-14 22:42   ` Sean Whitton
2022-09-15  5:33     ` Eli Zaretskii
2022-09-15 16:18       ` Sean Whitton
2022-09-15 16:48         ` Eli Zaretskii
2022-09-15 22:29           ` Sean Whitton
2022-09-14 19:17 ` Juri Linkov [this message]
2022-09-14 22:44   ` Sean Whitton
2022-09-15  6:59     ` Juri Linkov
2022-09-15 16:15       ` Sean Whitton
2022-09-15 17:27         ` Juri Linkov
2022-09-15 22:29           ` Sean Whitton
2022-09-16  6:59             ` Juri Linkov
2022-09-18 21:48               ` Sean Whitton
2022-09-19  6:42                 ` Juri Linkov
2022-09-20 22:54                   ` Sean Whitton
2022-09-21 18:52                     ` Juri Linkov
2022-09-21 19:39                       ` Sean Whitton
2022-09-22  6:39                         ` Juri Linkov
2022-09-22 16:10                           ` Sean Whitton
2022-09-22 18:44                             ` Juri Linkov
2022-09-22 21:20                               ` Sean Whitton
2022-09-23  6:42                                 ` Juri Linkov
2022-09-23 16:34                                   ` Sean Whitton
2022-09-24 19:20                                   ` Sean Whitton
2022-09-24 19:57                                     ` Juri Linkov
2022-09-24 23:18                                       ` Sean Whitton
2022-09-25  7:29                                         ` Juri Linkov
2022-09-26 22:33                                           ` Sean Whitton
2022-09-27 18:59                                             ` Juri Linkov
2022-09-28  1:15                                               ` vc-edit-next-command (was bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches) Sean Whitton
2022-09-28 17:53                                                 ` bug#57807: " Juri Linkov
2022-09-28 17:53                                                 ` Juri Linkov
2022-09-28 20:41                                                   ` bug#57807: " Sean Whitton
2022-09-28  1:15                                               ` Sean Whitton

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=86v8ppn5b2.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=57807@debbugs.gnu.org \
    --cc=spwhitton@spwhitton.name \
    /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.