All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhanusree <bhanusreemahesh@gmail.com>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [Outreachy Kernel][PATCH v3] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line
Date: Sat, 6 Oct 2018 23:59:02 +0530	[thread overview]
Message-ID: <c1c8d1b5-9e9c-9797-bbcc-4af9e9c2a826@gmail.com> (raw)
In-Reply-To: <20181006182737.GB7070@himanshu-Vostro-3559>

Please let me know what to do on this ?


On Saturday 06 October 2018 11:57 PM, Himanshu Jha wrote:
> On Sat, Oct 06, 2018 at 11:42:16PM +0530, Bhanusree wrote:
>>> Then please state that reasoning in subject too ...
>>> Subject: [PATCH v4] ....
>>
>>> ---
>>> changelog:
>>> v4: corrected whitespace error.
>>> v3: ...
>>> v2: ...
>> I made changes mentioned and sent already with Subject:[PATCH v4]. Am I
>> supposed to send it again?
> Ah, I see.
>
> Subject: [Outreachy kernel] Re: [Outreachy Kernel][PATCH v4] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line
>
> You send the patch as a "Re:" as you forgot to use `get_maintainer`
> in the first place.
>
> Took me some time to figure that out.
>
> And I think this is not the correct way.
>



  reply	other threads:[~2018-10-06 18:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 13:57 [Outreachy Kernel][PATCH v3] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line Bhanusree Pola
2018-10-06 14:07 ` [Outreachy Kernel][PATCH v4] " Bhanusree
2018-10-06 17:55 ` [Outreachy kernel] [Outreachy Kernel][PATCH v3] " Himanshu Jha
     [not found]   ` <68d61f32-294d-6056-7b3d-a89735bc539f@gmail.com>
     [not found]     ` <20181006180243.GG6283@himanshu-Vostro-3559>
2018-10-06 18:12       ` Bhanusree
2018-10-06 18:27         ` Himanshu Jha
2018-10-06 18:29           ` Bhanusree [this message]
2018-10-06 18:32             ` Himanshu Jha
2018-10-06 18:48               ` Bhanusree
2018-10-06 18:53                 ` Julia Lawall
2018-10-06 17:59 ` Himanshu Jha
2018-10-06 18:05   ` Bhanusree
2018-10-06 18:13     ` Himanshu Jha
2018-10-06 18:15       ` Bhanusree

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=c1c8d1b5-9e9c-9797-bbcc-4af9e9c2a826@gmail.com \
    --to=bhanusreemahesh@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=himanshujha199640@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 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.