From: Hans de Goede <hdegoede@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andy@infradead.org>,
Mark Gross <mark.gross@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>
Subject: Re: [GIT PULL] platform-drivers-x86 for 5.19-1
Date: Thu, 26 May 2022 21:58:02 +0200 [thread overview]
Message-ID: <82c37e1c-f216-e635-9107-af04f43484e4@redhat.com> (raw)
In-Reply-To: <CAHk-=wgTRT6nQeJpVCKb+m=So6bLzUZQYcY6+RH5W0gZfsp+Fg@mail.gmail.com>
Hi,
On 5/26/22 21:25, Linus Torvalds wrote:
> On Wed, May 25, 2022 at 5:34 AM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> 5. run:
>>
>> git tag -s platform-drivers-x86-v5.19-1 for-next
>> git request-pull v5.18-rc1 git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git platform-drivers-x86-v5.19-1 > pull
>
> So there's your problem.
>
> You're basically saying "give me a pull-request against v5.18-rc1".
>
> Which is bogus, since you already sent me part of your pile after rc1,
> and I already have it, so now your pull request will end up repeating
> those parts.
>
> So just do
>
> git fetch origin
> git request-pull origin/master git://git....
>
> to let git figure out what the actual common state is with 'origin'
> (and obviously you may have a different name for my upstream
> repository, so replace "origin" with whatever that correct name is).
>
> (That "git fetch origin" doesn't have to happen right before the pull
> request, but it has to be done at *some* point so that your git tree
> is basically aware of what I've merged from you previously).
>
> Anyway, the important point is that you shouldn't try to remember -
> incorrectly - what the last common point for us is. Git knows - as
> long as you just give it enough info.
Right, I see. I gave this a try locally and indeed reduces the shortlog
+ diffstat a bit. I will remember to use this form when creating
pull-reqs from now on.
Note that this seems to only help up to the point where my for-next
and fixes branching start diverging though.
So e.g. the surface bits you pointed out before:
platform/surface:
- aggregator: Fix initialization order when compiling as builtin module
- gpe: Add support for Surface Pro 8
+ the matching diffstat bits
Are still present in the shortlog even though they are already in v5.18
Regards,
Hans
next prev parent reply other threads:[~2022-05-26 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 20:00 Hans de Goede
2022-05-24 3:49 ` Linus Torvalds
2022-05-24 6:47 ` Hans de Goede
2022-05-24 17:17 ` Linus Torvalds
2022-05-25 12:34 ` Hans de Goede
2022-05-26 19:25 ` Linus Torvalds
2022-05-26 19:58 ` Hans de Goede [this message]
2022-05-24 4:27 ` pr-tracker-bot
2022-08-04 10:46 Hans de Goede
2022-08-05 1:28 ` 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=82c37e1c-f216-e635-9107-af04f43484e4@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®