From: Kari Argillander <kari.argillander@gmail.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: sfr@canb.auug.org.au, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Question about ntfs3 git pull request
Date: Sat, 25 Sep 2021 11:28:23 +0300 [thread overview]
Message-ID: <20210925082823.fo2wm62xlcexhwvi@kari-VirtualBox> (raw)
In-Reply-To: <89481e37-6723-6dd5-3549-85d1aa9fccbe@paragon-software.com>
On Fri, Sep 24, 2021 at 07:47:09PM +0300, Konstantin Komarov wrote:
> Hello, Stephen, Linus!
>
> I have a question about next git pull request.
>
> After first ntfs3 pull request [1] was accepted
> there are some new commits, that I want to send for rc5 probably
> (need more tests + some time in linux-next).
Imo you can send PR before rc5. No need to send head if you do not want.
Some of the patches has already been in linux-next almoust 3 weeks. Also
other people might want to test what we have done. Of course they are in
linux-next but many folks test Linus rc's so we want there patches also.
If we do massive commit dump to rc5 it is quite close already release
date and other people do not get testing time so much.
Argillander
> I've noticed, that I missed step
> "If your upstream-bound branch has emptied entirely into the mainline
> during the merge window, you can pull it forward with a command like"
> from Kernel Maintainer Handbook [2].
>
> Right now my github repo still based on 5.14-rc7.
> Do I need to update it with git merge up to 5.15-rcX?
> Or will it be ok to send git pull request as is and
> back merge master only when 5.15 will release?
>
>
> [1]: https://lore.kernel.org/linux-fsdevel/aa4aa155-b9b2-9099-b7a2-349d8d9d8fbd@paragon-software.com/T/#u
> [2]: https://www.kernel.org/doc/html/latest/maintainer/rebasing-and-merging.html#finally
prev parent reply other threads:[~2021-09-25 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 16:47 Question about ntfs3 git pull request Konstantin Komarov
2021-09-24 17:13 ` Linus Torvalds
2021-09-25 8:28 ` Kari Argillander [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=20210925082823.fo2wm62xlcexhwvi@kari-VirtualBox \
--to=kari.argillander@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.