On Tuesday, May 13, 2003, at 11:59 PM, Mark Grosberg wrote:
>
>
> On Tue, 13 May 2003, mark benedetto king wrote:
>
>> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=9845
>
> I took a look at this. It seems that Perforce does it, but has a crappy
> parser. I think my parser is quite intuitive. If you remove the marker
> line, the parsing is not done. If you alter the format of the part it
> is
> parsing, it errors out.
>
> It is an "alternative" interface to something that could be done on the
> command line. But it is a convenient one to some, none the less. On the
> bright side, it is relatively transparent. It's nice to know that after
> you type in a long log message the one file you added a "printf" in for
> debugging can be quickly removed as you do your final checks for your
> commit.
>
> How would Garrett feel about keeping this feature with a config option?
I'm ambivalent about it. Basically, if it's there, I'd rather not hide
it behind a config file, and i'd want to be sure that it's obvious from
looking at the template we load up that you can edit the list of files
(the 'everything below this line will be ignored' thing doesn't cut it,
since we're not ignoring it anymore). that said, I haven't looked at
the latest iteration of the patch, so perhaps you've dealt with that
already.
Honestly, I use the feature in perforce, but primarily because I can't
figure out how to tell perforce to do a 'p4 submit foo/bar.c
blah/baz.c'. You can do wildcards, but that only works if you want
everything in a directory, or you can do 'everything' and edit the
list, at least as far as I can tell. Subversion's current way of
dealing with it seems more intuitive, the perforce way seems like a bit
of a hack.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 13:47:52 2003