git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: git@vger.kernel.org
Subject: path-restricted log vs. subtree merges
Date: Sat, 15 Mar 2025 15:45:01 +0100	[thread overview]
Message-ID: <Z9WSbUQw4VBQiOqi@ugly> (raw)

in my quest to prepare for hacking git-gui, i ran

   cd .../git/git-gui
   git log .

the result is ... unhelpful. apart from a few commits that were done
directly in the git repo, there are only merges. notably, there is no
trace of the commits that are being merged (and the way gitk presents
this partial log is even more unhelpful).

i'm speculating that this is the result of git log not handling the
subtree merges in any way, with somewhat predictable consequences.

i suppose there is overlap with the fact that --follow works only for a
single file, which is also unfortunate. (a recent test case in the repo
would be templates/hooks.)

             reply	other threads:[~2025-03-15 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 14:45 Oswald Buddenhagen [this message]
2025-03-16 16:32 ` path-restricted log vs. subtree merges Johannes Schindelin
2025-03-16 19:44   ` Junio C Hamano
2025-03-17 17:43 ` Jeff King

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=Z9WSbUQw4VBQiOqi@ugly \
    --to=oswald.buddenhagen@gmx.de \
    --cc=git@vger.kernel.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.
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 NNTP newsgroup(s).