From: "Michael S. Tsirkin" <mst@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 0/7] git send-email suppress-cc=self fixes
Date: Mon, 10 Jun 2013 09:53:24 +0300 [thread overview]
Message-ID: <20130610065324.GA26501@redhat.com> (raw)
In-Reply-To: <7vy5ain9yg.fsf@alter.siamese.dyndns.org>
On Sun, Jun 09, 2013 at 04:25:11PM -0700, Junio C Hamano wrote:
> "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.
Unless I rerun with same vX :(
Would it make sense for it to check for vX existance and fail?
Same without -vX, when 000X exists ...
Could be an 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.
grep serves just as well but
I still need to copy it to the next line manually...
I vaguely remember there was some way to say
"head of the remote I am tracking" - but I could not find it.
Where are all the tricks like foo^{} documented?
I tried fgrep '{}' Documentation/*txt and it only returned
git-show-ref.txt which isn't really informative ...
Additionally, or alternatively, would it make sense for git format-patch
to format the diff against the tracking branch by default?
> > 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).
I still need to copy subject, Cc list and blurb to the next line manually.
Now that there's a concept of revisions,
maybe git format-patch -v4 could copy the text
and subject from v3?
--
MST
next prev parent reply other threads:[~2013-06-10 6:53 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
2013-06-10 6:53 ` Michael S. Tsirkin [this message]
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=20130610065324.GA26501@redhat.com \
--to=mst@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).