> Fitz and I were working on the client README, fleshing out commands
> and their options a couple nights ago. We came across and interesting
> idea (Fitz's really) for a feature that CVS does not have that
> Subversion might want to have (given that software can want anything).
> It's in the README, but I just wanted to draw attention to it to get
> some feedback from the group.
> Here is the snippet from the README:
> This is going to take a bit of explaining. Imagine an intelligent
> update that knows to add new files and remove files that you've
> removed, and all recursively (without having to svn add, svn rm, ad
> nauseam). More to come!
> We had originally thought that it might be an option to update, like:
> $ svn up --force
> But we reasoned that it might be better to have a separate command
> since it is so much more than just updating.
> So if I have a working copy like so:
> $ ls
> SVN/ main.c foo.c bar/
> where main.c is in the repository, foo.c needs a checkin and bar.c is
> absent from the repository.
> And I do:
> $ svn sync
> What happens is foo.c gets checked in and bar and its contents get
> automagically added and checked in.
Actually, I had envisioned it as Adding and Removing, not checking in.
So, for example, you've got:
$ ls -1
$ touch qux
$ touch qux/fizzle
$ touch qux/smootch
$ rm bar.c
$ svn sync
$ svn ci -m "Boy have I been busy."
* Note, that if you were to do an update at this point, bar.c would be
pulled from the repository
Received on Sat Oct 21 14:36:12 2006