From: Richard Weinberger <richard.weinberger@gmail.com>
To: sedat.dilek@gmail.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: Re: Merge branch 'l1tf-final' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Date: Thu, 16 Aug 2018 17:42:21 +0200 [thread overview]
Message-ID: <CAFLxGvxhUyqs3_esJwBjHrTY0Ba=bPB=425hWr0rz-BySTjzoA@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUW9Cg0G41ZSwjUBaJ+F9qCc23GGMp8aCgfNQejstKJmmQ@mail.gmail.com>
On Thu, Aug 16, 2018 at 2:58 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
> Hi Linus,
>
> I am here on Linux v4.18 and tried first to merge the l1tf-final Git-branch.
> Unfortunately, this is no more available in the tip Git-tree.
>
> Then I saw Linux v4.18.1 which includes all the above stuff.
>
> I tried to 'git cherry-pick -m 1 958f338e96f874a0d29442396d6adf9c1e17aa2d'.
> I know the commit-id is the hash of a merge.
> Luckily, I could get the "diff" and applied it.
> But the history misses.
>
> How can I get the history and subjects of all commits in your tree to
> cherry-pick the single commits?
>
> Do you happen to know another solution to get easily all L1TF commits
> with any other tricks?
That should help:
git log --oneline
958f338e96f874a0d29442396d6adf9c1e17aa2d^..958f338e96f874a0d29442396d6adf9c1e17aa2d
--
Thanks,
//richard
next prev parent reply other threads:[~2018-08-16 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 7:37 Merge branch 'l1tf-final' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Sedat Dilek
2018-08-16 15:42 ` Richard Weinberger [this message]
2018-08-17 6:58 ` Sedat Dilek
2018-08-17 8:33 ` Vegard Nossum
2018-08-17 8:55 ` Sedat Dilek
2018-08-16 17:14 ` Linus Torvalds
2018-08-17 7:14 ` Sedat Dilek
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='CAFLxGvxhUyqs3_esJwBjHrTY0Ba=bPB=425hWr0rz-BySTjzoA@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 NNTP newsgroup(s).