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: Tue, 24 May 2022 08:47:47 +0200 [thread overview]
Message-ID: <f39aa9c0-b4e6-1f5d-f556-643442fcbcc5@redhat.com> (raw)
In-Reply-To: <CAHk-=wgV8zqiLi5p-SNZ2zSi95CkkFXqPZJjtneVXeobgAohJg@mail.gmail.com>
Hi Linus,
On 5/24/22 05:49, Linus Torvalds wrote:
> On Sun, May 22, 2022 at 1:00 PM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git tags/platform-drivers-x86-v5.19-1
>
> Hmm.
>
> Your diffstat doesn't match what I get, and it seems to be because
> you've generated the diffstat based off v5.18-rc1, but you already
> sent me two pull requests with fixes since.
>
> So your diffstat contained the diffs from those fixes I had already gotten.
>
> If you just do "git fetch origin" (replace 'origin' with whatever you
> call the upstream tree) before doing the pull request, git would have
> figured that out.
I did do a "git remote update origin" recently (recent-ish), but
AFAIK that does not help.
I did read somewhere that in cases like this some maintainers
create a branch with a merge of their for-next branch into
say v5.18 in there and then they do a diffstat between the
merge and v5.18 and manually edit the pull-req to replace
the diffstat.
That makes sense to do if say some files have moved / been renamed
after rc1, but that seems overkill in this case since my fixes
pull-reqs weren't that big and did not include any moves/renames ?
Regards,
Hans
next prev parent reply other threads:[~2022-05-24 6:48 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 [this message]
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
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=f39aa9c0-b4e6-1f5d-f556-643442fcbcc5@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®