All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Bhagyashri Dighole <digholebhagyashri@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Outreachy <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH v3 1/2] staging: fbtft: Remove unused #defines.
Date: Wed, 6 Mar 2019 10:44:00 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1903061039180.3557@hadrien> (raw)
In-Reply-To: <CAOMPgjgrT3q67efW_nnbGU0qTi1DMEj=Siyy2FRSZOCG+dQAoA@mail.gmail.com>



On Wed, 6 Mar 2019, Bhagyashri Dighole wrote:

> On Wed, Mar 6, 2019 at 1:29 PM Julia Lawall <julia.lawall@lip6.fr> wrote:
> >
> > It would be good to have a cover letter (0/2) for this patch series as
> > well.
> >
>
> I used -n flag for generating cover letter because there is two patch series.

But it seems that there is no cover letter, or at least I did not receive
one.

The documentation for git format-patch says:

When multiple patches are output, the subject prefix will instead be
"[PATCH n/m] ". To force 1/1 to be added for a single patch, use -n. To
omit patch numbers from the subject, use -N.

So that doesn't seem like the right way to get a cover letter.  (Indeed, I
have noticed some patches with 1/1, which also seems unnecessary).  I
think you want the option --cover-letter.  This is discussed in the
"Versioning patchsets" section of the tutorial.

julia


  reply	other threads:[~2019-03-06  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  5:23 [PATCH v3 1/2] staging: fbtft: Remove unused #defines Bhagyashri Dighole
2019-03-06  7:59 ` [Outreachy kernel] " Julia Lawall
2019-03-06  7:59 ` Julia Lawall
2019-03-06  8:22   ` Bhagyashri Dighole
2019-03-06  9:44     ` Julia Lawall [this message]
2019-03-06 10:16       ` Bhagyashri Dighole
2019-03-06  9:11 ` Greg Kroah-Hartman
2019-03-06  9:31   ` Bhagyashri Dighole

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=alpine.DEB.2.20.1903061039180.3557@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=digholebhagyashri@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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.