threads / discuss / 1074

OOPS: unnumbered patch series

Subject: OOPS: unnumbered patch series

## tl;dr

3 messages between Jul 1, 2005 and Jul 1, 2005.

replies: 2people: 2as markdown or json

Jon Seymour· Jul 1, 2005, 06:34 UTC · lore

Sorry about that. I'll resend with each patch numbered in sequence.

I forgot that git-format-patch-script no longer numbers things by default.

Junio: this is an example where the special case would be good. As it
stands, I now have to add a special case to my wrapper around your
scripts to use the -n switch if and only if I have more than 1 patch
to send.

jon.

-- 
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/

Junio C Hamano· Jul 1, 2005, 07:01 UTC · re: Jon Seymour · lore

Re: OOPS: unnumbered patch series

>>>>> "JS" == Jon Seymour <jon.seymour@gmail.com> writes:

JS> Junio: this is an example where the special case would be good.

I do not think -n would number [PATCH 1/1]. Please try it and complain loudly if that does not work for you.

Jon Seymour· Jul 1, 2005, 14:56 UTC · re: Junio C Hamano · lore

Re: OOPS: unnumbered patch series

On 7/1/05, Junio C Hamano <junkio@cox.net> wrote:

Show 7 quoted lines

> >>>>> "JS" == Jon Seymour <jon.seymour@gmail.com> writes:
> 
> JS> Junio: this is an example where the special case would be good.
> 
> I do not think -n would number [PATCH 1/1].  Please try it and
> complain loudly if that does not work for you.
>

Apologises loudly :-)

jon.