From: Jeff King <peff@peff.net>
To: biswaranjan panda <biswaranjan.nitrkl@gmail.com>
Cc: Bryan Turner <bturner@atlassian.com>, git@vger.kernel.org
Subject: Re: Retrieving a file in git that was deleted and committed
Date: Sat, 8 Dec 2018 02:29:15 -0500 [thread overview]
Message-ID: <20181208072915.GA20697@sigill.intra.peff.net> (raw)
In-Reply-To: <CADHAf1bH5Aaw3-5WvoHawjXUXL9B-YNvh+AYU1fpGbUe=c0E+A@mail.gmail.com>
On Fri, Dec 07, 2018 at 01:50:57PM -0800, biswaranjan panda wrote:
> Thanks Jeff and Bryan! However, I am curious that if there were a way
> to tell git blame to skip a commit (the one which added the file again
> and maybe the one which deleted it originally) while it walks back
> through history, then it should just get back the
> entire history right ?
Not easily. ;)
You can feed a set of revisions to git-blame with the "-S" option, but I
don't offhand know how it handles diffs (I think it would have to still
diff each commit against its parent, since history is non-linear, and a
list is inherently linear). You might want to experiment with that.
Other than that, you can play with git-replace to produce a fake
history, as if the deletion never happened. But note that will affect
all commands, not just one particular blame. It might be a neat way to
play with blame, but I doubt I'd leave the replacement in place in the
long term.
-Peff
next prev parent reply other threads:[~2018-12-08 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 6:49 Retrieving a file in git that was deleted and committed biswaranjan panda
2018-12-07 6:55 ` Bryan Turner
2018-12-07 7:07 ` biswaranjan panda
2018-12-07 7:20 ` Jeff King
2018-12-07 7:37 ` Bryan Turner
2018-12-07 21:50 ` biswaranjan panda
2018-12-08 7:29 ` Jeff King [this message]
2018-12-09 0:07 ` biswaranjan panda
2018-12-11 1:19 ` Junio C Hamano
2018-12-10 21:33 ` Elijah Newren
2018-12-11 9:46 ` Jeff King
2018-12-10 15:12 ` Sergey Organov
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=20181208072915.GA20697@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=biswaranjan.nitrkl@gmail.com \
--cc=bturner@atlassian.com \
--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.
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).