From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>
Cc: ronnie sahlberg <ronniesahlberg@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Use less confusing branch name for populating ksmbd changes in for-next
Date: Thu, 30 Sep 2021 08:46:23 +1000 [thread overview]
Message-ID: <20210930084623.3391092d@canb.auug.org.au> (raw)
In-Reply-To: <CAH2r5mt_cFskiqbVvMn_M44p=0L-zFdkKsJj2JNYC3QLriEAXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Hi Steve,
On Wed, 29 Sep 2021 13:22:34 -0500 Steve French <smfrench@gmail.com> wrote:
>
> Can we switch from using "cifsd-for-next" branch to "ksmbd-for-next"
> when pulling changes
> automatically into linux-next (since the module is fs/ksmbd/ksmbd.ko
> using the branch name "ksmbd-for-next" is probably less confusing to
> some)
>
> ie from:
> https://github.com/smfrench/smb3-kernel/commits/cifsd-for-next
> to
> https://github.com/smfrench/smb3-kernel/commits/ksmbd-for-next
Done. I also renamed the tree in linux-next from cifsd to ksmbd.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-09-29 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 18:22 Use less confusing branch name for populating ksmbd changes in for-next Steve French
2021-09-29 22:46 ` Stephen Rothwell [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=20210930084623.3391092d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.com \
/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