[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220328103839.602a0d43@kernel.org>
Date: Mon, 28 Mar 2022 10:38:39 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: davem@...emloft.net, netdev@...r.kernel.org, pabeni@...hat.com,
corbet@....net, bpf@...r.kernel.org, linux-doc@...r.kernel.org,
f.fainelli@...il.com
Subject: Re: [PATCH net 03/13] docs: netdev: move the patch marking section
up
On Sun, 27 Mar 2022 18:28:35 +0200 Andrew Lunn wrote:
> > +How do I indicate which tree (net vs. net-next) my patch should be in?
> > +----------------------------------------------------------------------
> > +To help maintainers and CI bots you should explicitly mark which tree
> > +your patch is targeting. Assuming that you use git, use the prefix
> > +flag::
> > +
> > + git format-patch --subject-prefix='PATCH net-next' start..finish
> > +
> > +Use ``net`` instead of ``net-next`` (always lower case) in the above for
> > +bug-fix ``net`` content. If you don't use git, then note the only magic
> > +in the above is just the subject text of the outgoing e-mail, and you
> > +can manually change it yourself with whatever MUA you are comfortable
> > +with.
>
> Maybe we should consider removing the 'If you don't use git...' text.
>
> We want people to use git.
>
> Anybody who can correctly format a patch and get it passed their MTU
> and mail system without it getting corrupted not using git should be
> able to figure out how to set the subject line correctly.
Sounds good to me.
Powered by blists - more mailing lists