Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Nguyen Duc Thinh <ducthinh100812@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: use git switch to create branches
Date: Sun, 18 Oct 2026 19:54:34 +0800	[thread overview]
Message-ID: <atSzetKWYkoeELXr@wyuan.org> (raw)
In-Reply-To: <20261018062200.29256-1-ducthinh100812@gmail.com>

Hi Nguyen,

On 2026-10-18 13:22:00 +0700, Nguyen Duc Thinh <ducthinh100812@gmail.com> wrote:

> On Sat, Sep 26, 2026 at 14:45:45 +0800, Weijie Yuan wrote:
> >     \$ git checkout -t -b my-topical-branch master
> > +    \$ git switch -t -c my-topical-branch master
> >      Branch 'my-topical-branch' set up to track local branch 'master'.
> >      Switched to a new branch 'my-topical-branch'
> > 
> > @@ -882,7 +882,7 @@ notice that it will have the ``base-commit:`` trailer at the very
> >  bottom, which provides the reviewer and the CI tools enough information
> >  to properly perform ``git am`` without worrying about conflicts::
> > 
> > -    \$ git checkout -b patch-review [base-commit-id]
> > +    \$ git switch -c patch-review [base-commit-id]
> >      Switched to a new branch 'patch-review'
> >      \$ git am patches.mbox
> >      Applying: First Commit
> 
> Hi Weijie,
> 
> Thank you for putting this patch together and for the credit. The
> conversion to the modern command layout keeps the guide fully up to
> date with current Git usage practices.
> 
> Reviewed-by: Nguyen Duc Thinh <ducthinh100812@gmail.com>

Thanks for your review!

So sorry for forgetting to have you cc'ed on this patch, I wasn't using
git-send-email so it didn't automatically add your addresses from the
trailers.

And yes, I dived for some time and noticed that you haven't split this
part yet and sent it out. To prevent forgetting later, I decided to do
so. ;-)

Thanks.

      reply	other threads:[~2026-10-18 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26  6:45 [PATCH] docs: submitting-patches: use git switch to create branches Weijie Yuan
2026-10-18  6:22 ` Nguyen Duc Thinh
2026-10-18 11:54   ` Weijie Yuan [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=atSzetKWYkoeELXr@wyuan.org \
    --to=wy@wyuan.org \
    --cc=corbet@lwn.net \
    --cc=ducthinh100812@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.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