From: Junio C Hamano <gitster@pobox.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 0/7] git send-email suppress-cc=self fixes
Date: Sun, 09 Jun 2013 16:25:11 -0700 [thread overview]
Message-ID: <7vy5ain9yg.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 20130605201423.GB31143@redhat.com
"Michael S. Tsirkin" <mst@redhat.com> writes:
> With respect to this, and a bit off-topic, what's
> the best way to revise patch series?
>
> What I did, given series in patchvN-1/:
>
> rm -fr patchvN #blow away old directory if there
> # otherwise I get two copies of patches if I renamed any
Not needed with recent "git format-patch -v4" option.
> git branch|fgrep '*'
> # Figure out on which branch I am, manually specify the correct upstream I'm tracking,
> # otherwise I get a ton of unrelated patches.
git-prompt with PS1 you do not need this either.
> git format-patch --cover --subject-prefix='PATCH vN' -o patchvN origin/master..
Again, "git format-patch -v4 -o mt-send-email" will deposit the new
ones alongside the older round.
> vi patchvN/0000* patchvN-1/0000*
Same (i.e. "vi mt-send-email/v*-0000-*.txt).
next prev parent reply other threads:[~2013-06-09 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 18:10 [PATCH v4 0/7] git send-email suppress-cc=self fixes Michael S. Tsirkin
2013-06-05 19:28 ` Junio C Hamano
2013-06-05 20:14 ` Michael S. Tsirkin
2013-06-09 23:25 ` Junio C Hamano [this message]
2013-06-10 6:53 ` Michael S. Tsirkin
2013-06-10 7:29 ` John Keeping
2013-06-10 8:59 ` Michael S. Tsirkin
2013-06-10 7:52 ` Junio C Hamano
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=7vy5ain9yg.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mst@redhat.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).