From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] Driver core fixes for 5.7-rc7 - take 2
Date: Sun, 24 May 2020 15:28:29 -0700 [thread overview]
Message-ID: <CAHk-=wjdf_jR1TriXQWZpS+bs9RhdV_E_VD9_SXc_yQXC+yzFA@mail.gmail.com> (raw)
In-Reply-To: <20200524211221.GW33628@sasha-vm>
On Sun, May 24, 2020 at 2:12 PM Sasha Levin <sashal@kernel.org> wrote:
>
> (and I'd like to see the reverts too, so that I could apply that revert
> to Stable trees as well. If a revert doesn't show up in git log we might
> miss doing a backport of it).
Plain "git log" never simplifies anything at all.
Only when you ask for simplification will "git log" start skipping things.
That's things like "--grep=XYZ" to only ask for something that has a
pattern in the commit log. Or asking for a certain author. That's the
simplest kind of log simplification.
But saying "I'm only interested in changes to this pathname" is
another "please give me simplified history, only as it is relevant to
this pathname". And then it does exactly that. Including pruning out
whole branches that aren't relevant.
Trust me, it's the behavior you want. There's a reason we have
"--full-history", but it's not enabled by default.
But if you do want full history, you can still say so.
Linus
next prev parent reply other threads:[~2020-05-24 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 13:17 [GIT PULL] Driver core fixes for 5.7-rc7 Greg KH
2020-05-23 14:05 ` Greg KH
2020-05-23 15:29 ` [GIT PULL] Driver core fixes for 5.7-rc7 - take 2 Greg KH
2020-05-23 18:14 ` Linus Torvalds
2020-05-24 15:00 ` Greg KH
2020-05-24 15:38 ` Greg KH
2020-05-24 15:42 ` Sasha Levin
2020-05-25 7:33 ` Greg KH
2020-05-24 17:05 ` Linus Torvalds
2020-05-24 19:45 ` Sasha Levin
2020-05-24 21:12 ` Sasha Levin
2020-05-24 22:28 ` Linus Torvalds [this message]
2020-05-24 22:24 ` Linus Torvalds
2020-05-25 7:40 ` Greg KH
2020-05-23 18:30 ` pr-tracker-bot
2020-05-23 18:30 ` [GIT PULL] Driver core fixes for 5.7-rc7 pr-tracker-bot
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='CAHk-=wjdf_jR1TriXQWZpS+bs9RhdV_E_VD9_SXc_yQXC+yzFA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).