Adding -c to export?

Introduction

The -c/--change option indicates that an action should be taken
on the "change set" for a given revision. I believe this makes sense
in the case of export, in that exporting a particular revision would
export only those files that have changed in that revision.

Motivation

I've seen a number of requests for the ability to export just the files
that have changed in a particular revision, e.g. for updating a web
site. Often the cost of the working copy or having a firewall keeps
the website from being a working copy, and using update.

Implementation Considerations (My thoughts in ()'s)

Should export -c create any intermediary directories required to
represent the files changed? (Yes)

Should the default be to overwrite any existing files? (Yes)

-----

I haven't done a lot of exporting, or even been in the situations I
am describing, but I have seen them brought up on users several
times. Given this design proposal is not terribly detailed, but if
accepted I can file an enhancement bug on this. So I guess this
falls more in to the errant thought category than design, but I
thought I would toss it out there.

Josh

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 11 21:15:54 2006