From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the ext3 tree
Date: Mon, 9 Jan 2023 10:51:05 +0100 [thread overview]
Message-ID: <20230109095105.afvw25ntcvopgvub@quack3> (raw)
In-Reply-To: <20230108125156.30578c00@canb.auug.org.au>
Hello!
On Sun 08-01-23 12:51:56, Stephen Rothwell wrote:
> The following commits are also in Linus Torvalds' tree as different commits
> (but the same patches):
>
> ae9e9c7ff062 ("udf: Fix extension of the last extent in the file")
> 6d5ab7c2f7cf ("udf: initialize newblock to 0")
Yes, I'm sorry for the trouble. Linus considered the whole original pull
request too intrusive for rc3 so I've just cherrypicked the easy standalone
fixes and sent a pull request for those. I've now rebased my for_next
branch on top of Linus' tree to get rid of the duplicates (nobody depends
on my tree and there's enough time before the merge window opens so it
should be fine). If there's a better process how to handle such situations,
please tell me.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2023-01-09 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 1:51 linux-next: duplicate patches in the ext3 tree Stephen Rothwell
2023-01-09 9:51 ` Jan Kara [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=20230109095105.afvw25ntcvopgvub@quack3 \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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