From: Arnd Bergmann <arnd@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jakub Kicinski <kuba@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
workflows@vger.kernel.org,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Thomas Osterried <thomas@osterried.de>
Subject: Re: Driver graveyard
Date: Mon, 2 May 2022 17:33:05 +0200 [thread overview]
Message-ID: <CAK8P3a0AH5eou3vJxc+hH36giqjaivUeZL2heBVDSO8E+mCyMw@mail.gmail.com> (raw)
In-Reply-To: <Ym/2U0elJvJM3hmN@pendragon.ideasonboard.com>
On Mon, May 2, 2022 at 5:18 PM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>
> On a side note, navigating removals is something git doesn't make easy:
> git blame will tell when a line has been added (or modified), but
> figuring out when a line has been removed is more difficult. Or is it
> one of git's features that I simply don't know about ?
I find 'git log -p' to almost always be more useful than 'git blame'
when trying to
find out what happened to a file.
What I tend to do is to start with 'git grep $KEYWORD v3.0' (or
2.6.12, 4.0, 5.0 etc)
to see what file mentioned something, and then 'git log -p --
$FILENAME' to see the
commits leading up to the removal.
One bit I find missing though is for 'git log --follow' to track
renames from $FILENAME
to a new location, rather than following where it came from.
Arnd
prev parent reply other threads:[~2022-05-02 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 14:18 Driver graveyard Jakub Kicinski
2022-05-02 14:29 ` Jonathan Corbet
2022-05-02 15:10 ` Jakub Kicinski
2022-05-02 15:15 ` Juergen Gross
2022-05-02 15:18 ` Laurent Pinchart
2022-05-02 15:33 ` Arnd Bergmann [this message]
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=CAK8P3a0AH5eou3vJxc+hH36giqjaivUeZL2heBVDSO8E+mCyMw@mail.gmail.com \
--to=arnd@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=thomas@osterried.de \
--cc=torvalds@linux-foundation.org \
--cc=workflows@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 read-only IMAP folder(s) and NNTP newsgroup(s).