new svn command/feature
From: Lee Burgess <lefty_at_red-bean.com>
Date: 2000-10-20 19:29:25 CEST
Fitz and I were working on the client README, fleshing out commands
Here is the snippet from the README:
This is going to take a bit of explaining. Imagine an intelligent
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
So if I have a working copy like so:
where main.c is in the repository, foo.c needs a checkin and bar.c is
And I do:
$ svn sync
What happens is foo.c gets checked in and bar and its contents get
Likewise, if I had in my working copy a bat.c and previously removed
Anyway, the jist is that this could be a very powerful Subversion
And there is always the .svnignore file to take care of files you
This is a pretty rough description, but enough to generate feedback.
Thoughts? Criticism? Pros? Cons?
-- Lee P. W. Burgess <<!>> Manipulate eternity. Power is a symphony: Programmer <<!>> elaborate, enormous, essential. Red Bean Software <<!>> Dream the moment with a fiddle in summer email@example.com <<!>> and a knife in winter.Received on Sat Oct 21 14:36:12 2006
This is an archived mail posted to the Subversion Dev mailing list.