From: Stefano Brivio <sbrivio@redhat.com>
To: Deepak Varma <mh12gx2825@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH v2] staging: fbtft: Reformat longer macro definitions
Date: Thu, 12 Mar 2020 20:00:05 +0100 [thread overview]
Message-ID: <20200312200005.51569670@elisabeth> (raw)
In-Reply-To: <70084eb2-233f-48ad-b1ff-f6a22a1f49a0@googlegroups.com>
On Thu, 12 Mar 2020 09:32:52 -0700 (PDT)
Deepak Varma <mh12gx2825@gmail.com> wrote:
> On Thursday, 12 March 2020 20:10:04 UTC+5:30, Julia Lawall wrote:
> >
> > Thsi information goes below the --- so that it will be dropped when the
> > patch is applied. When someone looks through the git history they will
> > have no idea what "and earlier patch description" refers to.
> >
> > julia
> >
>
> Is this done at the time of "commit --amend" or should this be added in the
> email template manually before sending the patch?
I typically do it "manually" after git format-patch (especially because
for networking patches we write non-trivial stuff before ---, and
trivial stuff such as "new patch in series" or "no changes" after ---).
I just got to know about the --notes option of git format-patch, I
guess you could also check that out.
--
Stefano
prev parent reply other threads:[~2020-03-12 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 14:24 [PATCH v2] staging: fbtft: Reformat longer macro definitions Deepak R Varma
2020-03-12 14:39 ` [Outreachy kernel] " Julia Lawall
2020-03-12 16:32 ` Deepak Varma
2020-03-12 19:00 ` Stefano Brivio [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=20200312200005.51569670@elisabeth \
--to=sbrivio@redhat.com \
--cc=mh12gx2825@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.