From: Stefano Brivio <sbrivio@redhat.com>
To: Jaehee Park <jhpark1013@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: Finding Clean-up Tasks
Date: Fri, 1 Apr 2022 17:08:39 +0200 [thread overview]
Message-ID: <20220401170839.3919d0b4@elisabeth> (raw)
In-Reply-To: <20220401142803.GA38814@jaehee-ThinkPad-X1-Extreme>
On Fri, 1 Apr 2022 10:28:03 -0400
Jaehee Park <jhpark1013@gmail.com> wrote:
> On Thu, Mar 31, 2022 at 11:38:05AM -0700, Alison Schofield wrote:
>
> [...]
>
> > If you have a patch AND a question, you can send the patch
> > and put your question below the scissors line. For example,
> > you might see multiple instances of something but are not sure
> > the patch will be well-received. Fix one instance - and below
> > the scissor line ask you question: "There are 10 more of these
> > in this file, just want to sanity check that my approach here
> > is wanted." (If I were doing cleanup today, I'd use this tactic
> > for drivers/staging/iio checkpatch ERROR about octals.)
> >
>
> Thank you for advice! I had a question about where to put the questions
> in the patch. When you say scissor line, are we putting dashed lined
> somewhere in the patch and writing our questions?
Let's say this is the original patch as prepared by git format-patch:
--
This is a commit message.
Signed-off-by: you
---
file.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/file.c
index 148b06a..ceb10a6 100644
--- a/file.c
+++ b/file.c
@@ -927,7 +927,6 @@ int function(void)
-
--
you can put your question (or any kind of comment, really) there:
--
This is a commit message.
Signed-off-by: you
---
I'm not sure this patch does anything. Should it do something?
file.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/file.c
index 148b06a..ceb10a6 100644
--- a/file.c
+++ b/file.c
@@ -927,7 +927,6 @@ int function(void)
-
--
Those three dashes are also commonly called Signed-off-by-line, or
SoB-line (the term might refer to the line above, to the dashes, to the
line below, depending on whom you're speaking to :)).
> Or did you mean we should reply to our patch?
You can also do that. If you're really unsure, you can also add [RFC]
to the subject, before [PATCH], to make it clear you're asking for
comments rather than actually submitting a change, and then write your
questions, concerns or considerations directly in the commit message.
--
Stefano
next prev parent reply other threads:[~2022-04-01 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 18:38 Finding Clean-up Tasks Alison Schofield
2022-03-31 18:50 ` Alison Schofield
2022-04-01 14:28 ` Jaehee Park
2022-04-01 15:08 ` Stefano Brivio [this message]
2022-04-01 15:18 ` Jaehee Park
2022-04-01 15:14 ` Fabio M. De Francesco
2022-04-01 15:17 ` Jaehee Park
2022-04-01 15:20 ` Alison Schofield
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=20220401170839.3919d0b4@elisabeth \
--to=sbrivio@redhat.com \
--cc=alison.schofield@intel.com \
--cc=jhpark1013@gmail.com \
--cc=outreachy@lists.linux.dev \
/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.