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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Michael S. Tsirkin" <mst@xxxxxxxxxx> 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).

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]