From: Brian Norris <computersforpeace@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git-log: tracking deleted file in a repository with multiple "initial commit" histories
Date: Tue, 16 Feb 2016 13:24:29 -0800 [thread overview]
Message-ID: <20160216212429.GA39536@google.com> (raw)
In-Reply-To: <20160216204557.GB27484@sigill.intra.peff.net>
On Tue, Feb 16, 2016 at 03:45:57PM -0500, Jeff King wrote:
> See the section on History Simplification in git-log. But basically,
> when you specify a pathspec, git does not traverse side branches that
> had no effect on the given pathspec.
Thanks for the pointer. Is this done primarily for performance reasons,
or for UI simplicity (e.g., to avoid some kinds of double-counting)?
Seems like it generates unintuitive behaviors, but if it's helping block
other unintuitive behaviors, then maybe it can't be resolved easily.
FWIW, I quite often use git-log to look at the history of a deleted
file. Seems like a pretty big hole if the default behavior is going to
prune away the entire history of the file.
[...]
> If you want to see the full history, you can with "--full-history"
> (there are some other simplification possibilities, but I don't think
> any of them are interesting for your particular case).
--full-history gives me what I want (I'll admit, I didn't read through
all the other "History Simplification" documentation). Can I make this
the default somehow?
Brian
next prev parent reply other threads:[~2016-02-16 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 20:24 [BUG] git-log: tracking deleted file in a repository with multiple "initial commit" histories Brian Norris
2016-02-16 20:45 ` Jeff King
2016-02-16 21:24 ` Brian Norris [this message]
2016-02-16 22:29 ` Jeff King
2016-02-18 22:27 ` Brian Norris
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=20160216212429.GA39536@google.com \
--to=computersforpeace@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).