git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Cc: Derrick Stolee <stolee@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-log on a file, and merges
Date: Fri, 02 Aug 2019 12:32:28 -0700	[thread overview]
Message-ID: <xmqqtvazjrcj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAA01CspHCKA3itmTxFO1NeNB6DpdFx3CTbXKtO=TvtznLn_zAg@mail.gmail.com> (Piotr Krukowiecki's message of "Fri, 2 Aug 2019 21:21:28 +0200")

Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:

> At this moment I'm not sure myself if I consider this a bug or not.

This definitely is not a bug but is a designed and intended
behaviour.

Think of running "git log" without "--full-history" that is limited
with a pathspec as a tool to ask Git to show _one_ way (preferrably
the simplest one) to explain how the current contents in paths that
match the pathspec came to be.  The "just explain to me one way" is
not about machine performance but reducing the clutter in the output
to help human reader(s) reading an otherwise complex history.


  reply	other threads:[~2019-08-02 19:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02  9:38 git-log on a file, and merges Piotr Krukowiecki
2019-08-02 14:22 ` Derrick Stolee
2019-08-02 19:21   ` Piotr Krukowiecki
2019-08-02 19:32     ` Junio C Hamano [this message]
2019-08-03  8:31       ` Piotr Krukowiecki

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqtvazjrcj.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=piotr.krukowiecki@gmail.com \
    --cc=stolee@gmail.com \
    /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://80x24.org/mirrors/git.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).