> From: Mark Grosberg [mailto:mark@nolab.conman.org]
> Sent: Friday, May 09, 2003 9:46 AM
[...]
> > The docstring for this function should explain exactly what kind of
> > input it expects, what it'll parse and when it'll fail. I'm also a bit
> > worried about its silently doing nothing if it encounters something it
> > can't parse; I think that's a potential source of many surprises and
>
> If it gets something it can't parse, it aborts and whatever was parsed is
> checked in. I figured that's what people would want.
No way. I don't want part of my changes to be checked in and part left
hanging in my working copy. That might break the tree, and worse, my
change is suddenly N commits instead of 1.
> I can certainly make it return an integer of success/failure on parsing
> and abort the checkin if there is an error.
That seems like a much better idea.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 9 09:52:38 2003