William Uther <willu.mailingLists@cse.unsw.edu.au> writes:
> On Saturday, May 17, 2003, at 09:58 PM, plasma wrote:
>
> > On Fri, May 16, 2003 at 11:26:41PM -0500, cmpilato@collab.net wrote:
> >> plasma <plasmaball@pchome.com.tw> writes:
> >>
> >>> hi all,
> >>>
> >>> 'svn export' refuses to export source files into an existing
> >>> directory. Say, if I ran a 'svn export URL PATH', found I made a
> >>> mistake (maybe forget to commit a file, or export a wrong branch),
> >>> then rerun 'svn export URL2 PATH'. Because the PATH was created by
> >>> previous command, the second one will refuse to run. PATH should be
> >>> removed explicity by user, and I think it's annoying.
> >>
> >> I'm confused. If you started an export and then cancelled it because
> >> it was the wrong thing, why would you want your next export to
> >> effectively interleave its output with whatever cruft you now have on
> >> disk from your failed export?!
>
> There are other uses aside from this one. The others are not so
> horribly broken. I see it as analogous to untarring over an already
> existing dir. Not the common case, but sometimes useful.
Okay, I'm down with that.
> > Since the patch is here, if you core members find it acceptable, maybe
> > you would like to add a new option to complete this issue? I would be
> > appreciate since I prefer 'svn export' do things this way.
>
> This sounds like a job for --force.
Sound good to me.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 17 18:25:14 2003