git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: fuyao <fuyao@allwinnertech.com>,
	git@vger.kernel.org, 黄臻炜 <huangzhenwei@allwinnertech.com>
Subject: Re: Is cover letter can save changes?
Date: Tue, 20 Oct 2020 12:21:30 -0700	[thread overview]
Message-ID: <xmqqmu0gbt51.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <873629fb6c.fsf@yadavpratyush.com> (Pratyush Yadav's message of "Tue, 20 Oct 2020 15:53:39 +0530")

Pratyush Yadav <me@yadavpratyush.com> writes:

> On Tue, Oct 20 2020, fuyao wrote:
>
>> Hi:
>>    i have question about format-patch.
>>
>>    when use git format-patch with --cover-letter, we add information
>>    in the cover letter. and then, i must send patch with -v2, the
>>    information in the cover letter is lost in the v2 patch.
> ...
> You can try using `git branch --edit-description <branch_name>` and
> write the contents of the cover letter there. Then you can use the
> option `--cover-from-description` to use the branch description when
> generating the cover letter.

Another thing people are encouraged to do is to use the -o option to
store iterations of your series on disk, perhaps in the same
directory.  When you edit v2-0000-cover-letter.txt file, you can
then reference the previous one you've already sent easily that way.

      reply	other threads:[~2020-10-20 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20  7:05 Is cover letter can save changes? fuyao
2020-10-20 10:23 ` Pratyush Yadav
2020-10-20 19:21   ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqmu0gbt51.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=fuyao@allwinnertech.com \
    --cc=git@vger.kernel.org \
    --cc=huangzhenwei@allwinnertech.com \
    --cc=me@yadavpratyush.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).