kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Can't seem to find a maintainer for init/* files
Date: Mon, 21 Oct 2019 09:45:57 -0400	[thread overview]
Message-ID: <229661.1571665557@turing-police> (raw)
In-Reply-To: <20191021123115.GA72248@Paulos-MacBook-Pro.local>


[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]

On Tue, 22 Oct 2019 01:37:33 +1300, Paulo Miguel Almeida said:

> In a second approach:
> I tried making "git log" to list all the commits this particular file was involved in
> (so I could use --follow) but I ended up with loads of commits that change other sections
> of the file (not the lines we were looking for) and because of that I didn't feel like I
> was meeting the "'git blame' to show you the original 6 commits rather than the
> cleanup" rule.

Hint 1:  'git log' supports --no-merges which can simplify things sometimes.

Hint 2:   When specifying a commit, there is a ~ operator that can be used to advantage here.

So once you figure out which commit did the whitespace patching, it's easy to get
git blame to cough up what the tree looked like just before.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2019-10-21 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 21:33 Can't seem to find a maintainer for init/* files Paulo Almeida
2019-10-18 21:38 ` Paulo Almeida
2019-10-18 22:32 ` Greg KH
2019-10-18 23:53   ` Paulo Almeida
2019-10-18 23:25 ` Valdis Klētnieks
2019-10-21 12:37   ` Paulo Miguel Almeida
2019-10-21 13:45     ` Valdis Klētnieks [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=229661.1571665557@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=paulo.miguel.almeida.rodenas@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. 
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).