Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-13 Thread Jacob Keller
On Thu, Aug 10, 2017 at 11:42 AM, Junio C Hamano wrote: > Jeff King writes: > >>> > The above example made me wonder if we also want a format specifier >>> > to do the above without piping, but it turns out that we already >>> > have "log --format=%(trailers)", so we are good ;-) >>> >>> I was go

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Junio C Hamano
Stefan Beller writes: > On Thu, Aug 10, 2017 at 11:03 AM, Jeff King wrote: >> On Thu, Aug 10, 2017 at 04:02:46AM -0400, Jeff King wrote: >> >>> On Wed, Aug 09, 2017 at 08:21:47AM -0400, Jeff King wrote: >>> >>> > This series teaches interpret-trailers to parse and output just the >>> > trailers.

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Junio C Hamano
Jeff King writes: >> > The above example made me wonder if we also want a format specifier >> > to do the above without piping, but it turns out that we already >> > have "log --format=%(trailers)", so we are good ;-) >> >> I was going to say, I thought we had a way to get trailers for a >> comm

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Stefan Beller
On Thu, Aug 10, 2017 at 11:03 AM, Jeff King wrote: > On Thu, Aug 10, 2017 at 04:02:46AM -0400, Jeff King wrote: > >> On Wed, Aug 09, 2017 at 08:21:47AM -0400, Jeff King wrote: >> >> > This series teaches interpret-trailers to parse and output just the >> > trailers. So now you can do: >> > >> >

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Jeff King
On Thu, Aug 10, 2017 at 04:02:46AM -0400, Jeff King wrote: > On Wed, Aug 09, 2017 at 08:21:47AM -0400, Jeff King wrote: > > > This series teaches interpret-trailers to parse and output just the > > trailers. So now you can do: > > > > $ git log --format=%B -1 8d44797cc91231cd44955279040dc4a1ee

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Jeff King
On Wed, Aug 09, 2017 at 08:21:47AM -0400, Jeff King wrote: > This series teaches interpret-trailers to parse and output just the > trailers. So now you can do: > > $ git log --format=%B -1 8d44797cc91231cd44955279040dc4a1ee0a797f | > git interpret-trailers --parse > Signed-off-by: Hartmut

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Jeff King
On Thu, Aug 10, 2017 at 12:04:49AM -0700, Jacob Keller wrote: > >> $ git log --format=%B -1 8d44797cc91231cd44955279040dc4a1ee0a797f | > >> git interpret-trailers --parse > >> Signed-off-by: Hartmut Henkel > >> Helped-by: Stefan Beller > >> Signed-off-by: Ralf Thielow > >> Acked-b

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-10 Thread Jacob Keller
On Wed, Aug 9, 2017 at 10:19 AM, Junio C Hamano wrote: > Jeff King writes: > >> Parsing trailers out of a commit message is _mostly_ easy, but there >> area a lot of funny corner cases (e.g., heuristics for how many >> non-trailers must be present before a final paragraph isn't a trailer >> block

Re: [PATCH 0/5] make interpret-trailers useful for parsing

2017-08-09 Thread Junio C Hamano
Jeff King writes: > Parsing trailers out of a commit message is _mostly_ easy, but there > area a lot of funny corner cases (e.g., heuristics for how many > non-trailers must be present before a final paragraph isn't a trailer > block anymore). The code in trailer.c already knows about these cor