git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v4 0/7] git send-email suppress-cc=self fixes

From
MTMichael S. Tsirkin <mst@redhat.com>
Date
Jun 10, 2013, 06:53 UTC
Message-ID
<20130610065324.GA26501@redhat.com>
In-Reply-To
<7vy5ain9yg.fsf@alter.siamese.dyndns.org>
On Sun, Jun 09, 2013 at 04:25:11PM -0700, Junio C Hamano wrote:
Show 11 quoted lines
> "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.

Show 5 quoted lines
> > 	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?

Show 8 quoted lines
> > 	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
Previous: Junio C HamanoNext: John Keeping
Message 5 of 8 in “git send-email suppress-cc=self fixes”
  1. 0/7 git send-email suppress-cc=self fixesMichael S. Tsirkin, Jun 5, 2013
  2. Junio C HamanoJun 5, 2013
  3. Michael S. TsirkinJun 5, 2013
  4. Junio C HamanoJun 9, 2013
  5. Michael S. TsirkinJun 10, 2013
  6. John KeepingJun 10, 2013
  7. Michael S. TsirkinJun 10, 2013
  8. Junio C HamanoJun 10, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.