Re: On "interpret-trailers" standalone tool

2014-04-16 Thread Junio C Hamano
Junio C Hamano writes: > ... I am being > cautious here because I do not see us making the same mistake. s/do not/& want to/ Sorry for the noise. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: On "interpret-trailers" standalone tool

2014-04-16 Thread Junio C Hamano
Junio C Hamano writes: > ... I am looking at this > more from the angle of obtaining a useful building block, while you > seem to be thinking of this as a specialized tool for a narrow set > of specifkc tasks. By the way, I am speaking with a bitter experience of designing the original "format-

Re: On "interpret-trailers" standalone tool

2014-04-16 Thread Junio C Hamano
Christian Couder writes: > If the input comes from stdin, then I agree that the command should be > a filter, so its output should be on stdout. But if the input comes > from files given as arguments, then I would say that the command > should behave as an editor and by default it should edit its

Re: On "interpret-trailers" standalone tool

2014-04-16 Thread Christian Couder
On Mon, Apr 14, 2014 at 11:41 PM, Junio C Hamano wrote: > Christian Couder writes: > >> Yeah, except that we could add for example a '-o' option that would >> take a directory as argument and that would mean that the command >> should operate on all the files in this directory. It would be like >

Re: On "interpret-trailers" standalone tool

2014-04-14 Thread Junio C Hamano
Christian Couder writes: >> However, I am wondering if the current "everything on the command >> line is instruction to the command" is too limiting to allow the use >> of the tool both as a filter and as a tool that can work on one or >> more files named on the command line. If we start from th

Re: On "interpret-trailers" standalone tool

2014-04-12 Thread Christian Couder
From: Junio C Hamano > > So far I've mostly been ignoring how the command line would look > like, I don't really feel this way ;-) > because the intermediate goal to my mind was to have it as a > hook that are added by people better versed with Git than an average > end-user, and if the command

On "interpret-trailers" standalone tool

2014-04-09 Thread Junio C Hamano
So far I've mostly been ignoring how the command line would look like, because the intermediate goal to my mind was to have it as a hook that are added by people better versed with Git than an average end-user, and if the command line interface had to change then they are capable of updating it, so