Separator character change for files ({files} key) in log

Berkes Adam adam.berkes at intland.com
Wed Nov 26 12:42:59 CST 2008


Bill Barry írta:
> Berkes Adam wrote:
> ...
>
> I too would like to see a solution to this problem, but I am not sure 
> this is the way to go. It seems to me that what we need for this is 
> some sort of higher level approach. Spaces or semicolons are fine for 
> a command line output when it will be read by people, but it should be 
> configurable somehow.
>
> For instance in my CCNET mercurial patch I could really use some kind 
> of --template parameter setting which would surround each individual 
> file with an xml tag (it would provide a much more elegant solution 
> than having to do a string.split on ';' after already doing an xml 
> parse on the output.
>

I don't want to say, there is no more elegant solution, but anyway: this 
is a command line output, which will generate some ambigous information 
for a file list. I cannot see now (in majority of normal use-cases) why 
an xml tag surrounding is better from a template, if the current output 
structure is flat text oriented. I prefer a full xml based resultset of 
log data, and allow xslt transformation templates on them (to generate 
command line output), but that is a bit of a cost.
I also don't want to defend my solution because it is minimal (from 
flexibility perspective).

A


More information about the Mercurial-devel mailing list