Versions doesn’t have UI for it, but you can use `svn switch` in Terminal to
point a working copy to a new repository location. Hopefully that will help.
http://svnbook.red-bean.com/en/1.6/svn.ref.svn.c.switch.html
Cheers,
- Quinn
On Dec 20, 2013, at 10:29 AM, Thinsoldier
Versions is almost unusable for me on Mavericks as well, but for different
reasons. It will frequently stop responding to clicks, often after
force-deleting an unversioned file (such as a .diff file I’ve saved locally for
a bug I’m working on). Relaunching Versions solves the problem for a
When I copy/move a file within my working copy, it shows with a green + icon,
and doesn’t allow me to Show Local Changes for the file, but `svn diff` gives
the correct result.
When a file has history with the addition (which is the case for move and
copy), it should be possible to view the
I'm not aware of a way to mark a versioned file such that Subversion won't ever
try to commit changes to it. You'd have to manually select (via command-click)
your hierarchy of files to exclude the files in question. I think the general
pattern to deal with such situations is to create template
I just implemented this for my own app, and it was a simple matter of using
-[NSWorkspace activateFileViewerSelectingURLs:]. I'd love to see this in
Versions.
http://stackoverflow.com/questions/7652928/launch-osx-finder-window-with-specific-files-selected
Thanks,
- Quinn
smime.p7s
Man, judging by the list traffic alone, you'd think we users are all endlessly
demanding and ungrateful wretches. Months of people kvetching about lack of 1.7
support and not knowing when it was coming. Now it's here, and the the first
post that mentioned 1.2 was about the new icon. (A valid
The last point is what tipped me off. There is almost certainly an invisible
.svn folder inside the .workspace folder. It contains information about the
associated repository, which is why Subversion thinks it already exists.
Cleaning out the .svn folder (at each level of the hierarchy, if
Merging and reintegrating is currently not supported from within Versions. I
personally use Terminal for these actions.
- Quinn
On Jul 11, 2012, at 10:46 AM, Peter Shaw wrote:
Hi,
i am interested in a goog svn client for mac. I am a heavy branch and
reintegrate guy and can't find a
I have the same complaint. My solution is to just modify the working copy via
Terminal after checking it out:
$ svn switch --relocate http://usern...@example.com http://example.com
/path/to/working/copy
This removes the username from the URL and avoids having to take it out by hand
when you
Since everything (except Xcode.app) which was in /Developer has moved inside
Xcode.app, it may help to switch your Developer directory location. For
example, in Terminal:
$ xcode-select -switch /Applications/Xcode.app/Contents/Developer
If that doesn't help, you can modify the path in
My guess was that Oliver may have meant using the SVN libraries via API, rather
than wrapping and parsing output from the command-line binary. My understanding
is that SVN only adds API variants and never takes away old ones, so backwards
compatibility is preserved. Now, linking against the
I think this is a general Subversion issue, and not something Versions alone
can address.
One thing folks I know often do is store a generic template file in the
repository, then add an svn:ignore property to ignore versions with local
modifications. For example, if you have foo.conf, you
I work on a project with several externals which rarely change. It's quite
annoying that when I select Changed, the entire paths down to all externals are
expanded, even though nothing has changed (either locally or remotely) for
those items. Collapsing the paths manually works only until the
I really like the View Show Updates from Repository option, since it alerts
me to changes that I haven't yet pulled from the repository. However, my main
project unfortunately resides on a rather slow SVN server (out of my control).
When I open a working copy bookmark for this project (in
23:54 schrieb Quinn Taylor:
Glad to see the 1.1.9 update, even though the changes are fairly minimal.
I'm looking forward to further improvements. Cheers to you, folks at Black
Pixel!
- Quinn
--
You received this message because you are subscribed to the Google Groups
Versions group
Shame I had to read about it via Daring Fireball first, but I'm excited that
Versions will be getting some love again. :-)
http://daringfireball.net/linked/2011/10/19/black-pixel
http://blackpixel.com/blog/1217/versions-and-kaleidoscope/
- Quinn
smime.p7s
Description: S/MIME cryptographic
This is not currently possible in Versions, and I'd like to see it added as
well. I think a better general-purpose solution would be to add checkboxes for
each table row in the commit sheet, allowing users to selectively omit
resources they don't want to commit. I've asked for that before, but
Can you please change it to include the revision number of the commit? Using
`svn commit` provides this info, and it would be very useful to have in the
notification.
Thanks,
- Quinn
smime.p7s
Description: S/MIME cryptographic signature
If the database.php file needs to be versioned (present in the repository),
then the solution you want isn't to ignore the file, because it has a different
meaning to Subversion, and hence Versions. Various SVN clients have their own
means to allow you to items you don't want to commit from
Yes, Subversion can ignore such patterns, but you'll need to specify that
pattern on the global-ignores line of your ~/.subversion/config file. For
reference, here's mine:
global-ignores = *.o *.lo *.la .*~ *~ ._* .DS_Store .Trash* *.pbxuser *.mode*
*.perspective*
- Quinn
On May 9, 2011, at
You should be aware that this is primarily a user list. The developers monitor
it as they have time, but the support email (now CC'd) is the best place to ask
such questions.
- Quinn
On May 3, 2011, at 9:28 AM, etapombas wrote:
solutions?
i'm still waiting
--
You received this
The core problem is that Versions supports SVN (Subversion) but not CVS. Thus,
Versions will never be able to connect to a CVS repository.
I highly recommend switching to SVN if at all possible. Here are some useful
resources.
http://subversion.apache.org/
This is one reason why I suggested to the devs that Timeline and Transcript
don't really belong as browsing modes: you can't perform any useful application
actions in these views, they really just provide accessory information.
Cornerstone has separate views for these features, which I like.
inline: Screen shot 2011-03-02 at 7.32.34 AM.png
I have View Show Updates from Repository enabled, and it's mildly annoying
that files added on the server have a generic document icon; it makes glancing
at the icon to infer what type it is rather useless. Using -[NSWorkspace
iconForFileType:]
I frequently get annoyed that the only way to select which columns are visible
is through a sub-menu of View. Please add the behavior like Mail has in the
message viewer, where right-clicking in the table header displays a contextual
menu that allows the user to (un)check a column. (I
How else would you recommend you refer to multiple versions of a file?
Realizing of course that the folks at Sofa used the name first, the term seems
(to me) more apt for the Lion feature than for a SVN client. I don't foresee
much (if any) more confusion over the name than exists today — I
When right-clicking on a bookmark, Delete Bookmark appears all the way at the
bottom, far from any similar commands. Please consider moving it to just below
the Edit and Duplicate menu items. Perhaps it was intentionally placed at the
bottom so people don't click it accidentally, but it takes
A conflict occurs when you update a file, and changes from the repository
conflict with changes local to your working copy. (Incidentally, this can
happen even with only one person working in a repository; I've occasionally
made changes to fix different things in different working copies, then
.
Maybe I'm missing something?
On Feb 7, 9:16 pm, Quinn Taylor quinntay...@mac.com wrote:
Are you talking about auto-completion of code symbols in the context of
writing a log message when committing?
- Quinn
On Feb 7, 2011, at 1:02 PM, dave wrote:
{first post here, please be nice
if adding support for ctags would be achievable?
Also, you didn't seem off-putting to me.
On Feb 9, 2011, at 11:17 AM, Quinn Taylor wrote:
Disclaimer: Sometimes my tone seems confrontational, but I'm really being
nice. I just tend to looks at things objectively and pragmatically. Please
don't
Are you talking about auto-completion of code symbols in the context of writing
a log message when committing?
- Quinn
On Feb 7, 2011, at 1:02 PM, dave wrote:
{first post here, please be nice :)}
in other version control clients, a useful feature is autocomplete of
function or script
I used to like the new mode selector okay when 1.1.x first came out, but I like
it less as time goes by. The biggest reason is that the vertical lines
frequently line up with table column dividers and create visual confusion; when
I go to manually resize columns, it's easy to accidentally try
Is it safe to assume your Mac is PowerPC rather than Intel? If so, the change
actually came with 1.1.x, you'll need to revert to 1.0.9.
http://groups.google.com/group/versions/browse_thread/thread/31c1504c154a5e25
Unfortunately, the link
can modularize most well formed code
bases.
On Jan 10, 11:45 am, Quinn Taylor quinntay...@mac.com wrote:
This is a workaround, but definitely annoying. Command-clicking sometimes
works, but sometimes not. For example, if I want to commit changes to a
directory's properties
Are you talking about their position in the toolbar? You can move those
yourself without touching the .xib file; it's a standard NSToolbar behavior in
Cocoa apps. Just select View Customize Toolbar... or right-click in the
toolbar and choose Customize Toolbar... to bring down a panel which
This is a workaround, but definitely annoying. Command-clicking sometimes
works, but sometimes not. For example, if I want to commit changes to a
directory's properties, but not changes within the directory itself. I end up
having to use Terminal and the --depth option.
I requested the
My first comment is that storing intermediate binary files (like .o and .pyc)
in Subversion is fairly irregular and not something I would recommend. My
approach is that if it can be generated from the source, it probably shouldn't
be in version control, particularly binary files which are
I agree, this has come up before and I have never found the username in the URL
to be useful, only ever annoying. When checking out a working copy via
Versions, one of my first steps tends to be opening Terminal and typing `svn
switch --relocate http://usern...@server/path http://server/path
Suppose I'm working on a branch which resides at /branches/my_branch and want
to merge changes from /trunk. I have a working copy for the branch only — since
it was checked out with Versions, the URL (from `svn info`) is
http://usern...@example.com/svn/branches/my_branch;. To merge changes made
Given the requests for Git support (which aren't actually a good fit for
Version, IMO) I thought this might be of interest.
http://www.git-tower.com/
Hey devs, this has some nice features that could work for SVN as well. ;-)
- Quinn
smime.p7s
Description: S/MIME cryptographic signature
:
Well I take it this is not supported and given the lack of team
response it won't be in the future either...
On Oct 11, 7:08 pm, Quinn Taylor quinntay...@mac.com wrote:
It's true, no merge on the feature list.
http://www.kaleidoscopeapp.com/
Notice the emphasis on *spotting* changes
On Oct 14, 2010, at 8:22 AM, Robert Goldman wrote:
On Oct 11, 12:05 pm, Quinn Taylor quinntay...@mac.com wrote:
I don't know of a way to do that in Versions, but I believe that
command-line svn will allow it. Type `svn help commit` in Terminal and look
at the --depth option. I believe
I don't know of a way to do that in Versions, but I believe that command-line
svn will allow it. Type `svn help commit` in Terminal and look at the --depth
option. I believe that --depth empty is the equivalent of --non-recursive
(which is now obsolete).
It's true, no merge on the feature list.
http://www.kaleidoscopeapp.com/
Notice the emphasis on *spotting* changes quickly. Merge is not yet supported,
but I imagine it will have to in order to survive and thrive amid competitors
which *do* support merging.
- Quinn
On Oct 11, 2010, at 9:58
You'll want to modify the [auto-props] section in your ~/.subversion/config
file. You can set svn:keywords=Revision for any matching pattern you like. This
will cause any SVN client to automatically apply that property (and any others)
when adding matching files.
Manually applying the property
I've had the opposite experience — for me, Versions handles external
modifications smoothly. Whether I'm working from Terminal, Xcode, or via ssh,
Versions picks up changes pretty quickly, and doesn't crash for me.
Regardless of which tool you use, Subversion actually locks a working copy when
Versions pick up changes smoothly when you delete something from your
working copy outside of versions? If so, I must be doing something wrong.
On 13 Sep 2010, at 19:52, Quinn Taylor quinntay...@mac.com wrote:
I've had the opposite experience — for me, Versions handles external
I think Versions could probably be a bit smarter about failed authentications
on the same server, but given the variety of ways hostnames can be written,
this is a difficult problem. (Not trying to make excuses, just sayin'...)
One workaround is to manually change the passwords in Keychain
FWIW, I don't get this on my machines, Versions idles at 0% CPU, and I've been
logged in for several days, with Versions running basically the whole time.
- Quinn
On Jul 2, 2010, at 2:33 AM, jayjay wrote:
Yes, this happens to me too. Just launch your Activity Monitor and
you'll see
Not through Versions. This requires special setup on the server to edit commit
properties anyway, and it's viewed as bad form (in the general case) to modify
comments after the fact — depending on your preference, correcting things like
typos can be an exception, but it's uncommon enough that I
Which feature?
On Jun 15, 2010, at 10:38 PM, Yoav wrote:
Also need this feature
--
You received this message because you are subscribed to the Google Groups
Versions group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to
, but still completely lost...
On May 12, 5:27 pm, Quinn Taylor quinntay...@mac.com wrote:
From Terminal, you'll want to look at using `svn merge --
reintegrate ...` — you can find more detail by typing `svn help
merge`. This assumes you're using SVN 1.5+. Also check out the SVN
book
This is correct. You can view the URL the working copy points to with the
inspector (Information tab) inside Versions, or by typing `svn info` in
Terminal while inside the working copy directory.
Versions doesn't yet have the ability to perform a `svn switch` operations, but
changing the URL
Are these directories already versioned in the repository? If so, you would
have to delete them first and commit, then set the svn:ignore property for the
containing directory.
- Quinn
On May 12, 2010, at 8:56 AM, si...@vg wrote:
I am pretty new to this so apologies if I am being dense
The svn:ignore property isn't recursive, so you must set it for the folder
which contains the resource. You can edit it by hand, but since Versions is a
GUI, a simpler way is to right-click on a file or folder and select Ignore X.
That will automatically set the property for you. However, it
I think it would be a nice feature, but the lack of response is probably
because use of SVN externals is not so common compared with other SVN features.
A GUI equivalent to `svn update --ignore-externals` would be nice, but I'd
venture a guess that things like merging and switching are more
If you're importing a new resource directly to the repository, then they have
to be serial, but when staging changes in a local working copy, adding a
resource tells SVN that it should be added when that particular resource path
is committed, but I find it most useful to add multiple items and
A working copy is a directory structure that contains metadata that associates
it with a repository. (It has invisible .svn directories throughout.) You
can't just add a normal folder without adding the content to a repository.
If you don't have a repository you want to store it in, you'll need
An easier way than typing all the filenames to ignore is to right-
click on a resource and select Ignore from the contextual menu that
pops up. Still, that's not to say that a non-modal window wouldn't be
nice to have...
Quinn
Sent from my iPod
On Mar 18, 2010, at 8:19 AM, Robert Goldman
You have two options:
1) Edit ~/.subversion/config by removing *.a from the line that begins with
global-ignores.
2) Manually add the file by using Terminal: svn add /path/to/lib.a
Good luck,
- Quinn
On Mar 8, 2010, at 7:02 AM, BostonMerlin wrote:
Sorry, i found the conf file but dont know
I think most people would think of this as a non-feature. Personally,
auto-commit is a feature I'd rather Versions NOT have. Programmers (one of the
most common users of Subversion) want to test before committing changes. Also,
it's generally poor practice to commit without a meaningful log
That's a helpful idea, I wouldn't mind seeing that.
As a sidenote, using skitch.com to share images like that one is often much
simpler. :-)
- Quinn
On Mar 1, 2010, at 10:40 AM, hanns wrote:
http://docs.google.com/Doc?docid=0AY8nEoeF09GOZGQ1ZGtkd3FfMmQyZnZ6dmdzhl=en
not sure anyone use
I have seen something similar on occasion, but it seemed that the filenames got
mixed up, so one or more of the FileMerge diffs transformed one document into
another. Closing the diff windows and re-issuing the command seemed to fix the
problem. It might be a race condition or just not matching
Is the file/folder you're trying to ignore already in the repository? You can
only ignore items that are within a versioned directory (not nested within one
or more unversioned folders), and that haven't been added to SVN themselves.
Hope that helps,
- Quinn
On Jan 16, 2010, at 2:33 PM,
Judging based on other people's problems may not be the wisest choice, though.
I personally have been using Versions since the beta, and there have been minor
bumps, but on the whole I've been very satisfied and have had very few issues.
Versions has quickly become an important part of my
Do you get the same problems accessing this URL via Terminal?
On Jan 7, 2010, at 3:07 PM, mort8104 wrote:
Am I missing something here?
I am running a Subversion daemon on my NAS box as per this procedure:
On Jan 7, 2010, at 3:42 PM, mort8104 wrote:
Thanks for your amazingly quick reply Quinn : )
Well, yes. The problem is identical.
My apologies - I should have tried that before posting.
With anon-access = none I get:
svn: No access allowed to this repository
With anon-access =
Another (perhaps simpler) way to do this is to use the package installers at
http://www.collab.net/downloads/community/ instead. The binaries will be
installed in /opt/subversion so they don't collide with the built-in SVN 1.4.4
tool set.
Alternatively, you can make Versions use SVN 1.4
It's possible that either the directory has its svn:ignore property set to
include *.a and/or your local subversion client config is set to do the same.
If you do `svn status` on the same directory in Terminal, do you see the files?
If not, the problem is wider that just Versions.
- Quinn
On
Agreed. Versions performs admirably for me, and I'm not afraid to use Terminal
to accomplish tasks it doesn't yet support. Just remember, that's what we used
to have to do, for everything, back when there were no GUIs... ;-) I'm not
saying I don't want to see the features, but I'm not one to
It would probably be faster and simpler to use http://www.skitch.com/ or
something similar for posting shots like this. (I don't have an answer for your
question, unfortunately.)
On Dec 11, 2009, at 10:38 AM, Weitdenker wrote:
Here you can see the error in a Screenshot:
Trying it out right now. I haven't been experiencing most of the issues
addressed, but the improvements are certainly welcome. :-)
- Quinn
smime.p7s
Description: S/MIME cryptographic signature
Since it's a file URL, you don't use 'localhost' as you would in a web URL. Try
this instead:
file:///Users/jtsm/Repositories
You do indeed need a third '/' since it represents starting from the root of
your boot volume.
- Quinn
On Dec 4, 2009, at 7:43 AM, Slack wrote:
Hi All,
OS X
it on Versions. :-)
- Quinn
On Dec 4, 2009, at 1:55 PM, Slack wrote:
Quinn,
Versions puts localhost in 'auto-magically'
I tried what you had before already with no success.
Thanks,
-Jason
On Dec 4, 8:12 am, Quinn Taylor quinntay...@mac.com wrote:
Since it's a file URL, you don't use
~/Repositories]$ svn list file:///Users/jtsm/Repositories/
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///Users/jtsm/Repositories'
So not versions, but Subversion, but still cryptic, I dont know how to
fix this.
-Jason
On Dec 4, 2:27 pm, Quinn Taylor quinntay
Your working copy is probably still hitting the old host — use the Inspector in
Versions or `svn info` to verify. Versions doesn't support svn switch yet. Look
at `svn help switch` for information on how to --relocate your repository root
URL.
- Quinn
On Dec 3, 2009, at 11:52 AM, kenja wrote:
nicely again, thanks for the help!
On Nov 24, 1:01 pm, Quinn Taylor quinntay...@mac.com wrote:
Only in the sense that they will not be readable by an earlier SVN
client. (It won't actually modify the working copy, it's a version
compatibility issue.)
- Quinn
On Nov 24, 2009, at 12:24 AM
I'll be a contrary example. Versions works flawlessly for me on Snow Leopard
with SVN 1.6.5, and on other machines with custom 1.6.6 binaries installed.
- Quinn
On Nov 23, 2009, at 4:56 AM, oltbaba wrote:
Which subversion version are you using?
We are experiencing problems with subversion
It's a matter of workflow preference. Yes, you can select files and folders in
the main GUI before committing — command-clicking etc. obviously works, but
just because something is possible doesn't mean that's the only way anyone
would/should ever want to do it. (Exhibit A: Windows) However, it
.
-Hardy
On Nov 19, 2009, at 10:50 AM, Quinn Taylor wrote:
It's a matter of workflow preference. Yes, you can select files and folders
in the main GUI before committing — command-clicking etc. obviously works,
but just because something is possible doesn't mean that's the only way
anyone
for a small project, but I found it
extremely annoying to use.
-Hardy
On Nov 19, 2009, at 10:50 AM, Quinn Taylor wrote:
It's a matter of workflow preference. Yes, you can select files
and folders in the main GUI before committing — command-clicking
etc. obviously works, but just
True. I was about to write the same thing, but I realized he got it right the
second time at the bottom of the email. :-)
On Nov 18, 2009, at 9:41 AM, Rob Rye wrote:
The subversion website is
http://subversion.tigris.org (note there is no u but rather a second i in
tigris).
Rob
You can make tags by doing this operation in the associated Repository
bookmark, rather than the Working Copy bookmark.
- Quinn
On Oct 28, 2009, at 9:24 AM, WalleniuM wrote:
yeah. but i have to checkout the whole repo to do that. or am i wrong?
i just have one folder, and want to create a
28, 2009, at 12:55 PM, WalleniuM wrote:
that could work.. but a direct option would be more accurate..
On 28 Okt., 18:20, Quinn Taylor quinntay...@mac.com wrote:
You can make tags by doing this operation in the associated
Repository
bookmark, rather than the Working Copy bookmark.
- Quinn
I'm also very appreciative of Marc's contributions. However, bear in
mind that this is very clearly an It would be nice if... enhancement
request that doesn't affect day-to-day usability like the crasher bugs
do — this is polish that would make the product nicer, but not a
critical fix.
Move the new folders with the same names out of the repository, then
update the working copy — Subversion should restore your deleted
folders. If you really want to delete them, do it from within Versions
(or svn) and commit before adding in the replacement directories. Or
just remove the
Check under View File Browser Columns. I think Properties Status
is the one you're looking for.
In all honesty, it would be nice if this were collapsed into the Data
Status column, since (I believe) the properties are either modified or
not — there is no state for added/deleted
You use Add locally, rather than Import. Generally speaking,
import is only for adding from your computer directly to the
repository. Normal workflow is to add files in a working copy, then
commit as a group when you're ready.
- Quinn
On Oct 20, 2009, at 3:53 AM, tonthomas wrote:
I
:35 AM, Joey Gibson wrote:
On Wed, Oct 14, 2009 at 1:26 PM, Quinn Taylor quinntay...@mac.com
wrote:
Yes, you should ignore it before commit. Since it is now
versioned (in the repository) you must first delete it, then
ignore it, then commit.
Also remember that you can do global ignores
I totally agree. I write mostly Java at work, and the deep package
hierarchies lead to lots of folders and few files being changed.
Additionally, command-clicking to (de)select works, but doesn't scale
so well when it's hard to tell whether a file is 7 or 8 levels deep,
if 2 that are 10-20
+1 This would be quite nice. In Eclipse, the Subversive plugin puts a
checkmark by each item to select whether it should be part of the
commit. The trick (as always) is how best to provide the desired
functionality in a tasteful and useful way, not just spewing
information all over the
I think he's probably talking about something like `svn switch`, in
which case no, Versions doesn't yet provide a quick way to do that.
Creating multiple working copies is one way to go, but the idea behind
svn switch is that SVN can modify/add/delete only the files that are
different
+1 from me as well. (I'd rank this as a lower-priority feature, but
still nice to have.)
- Quinn
On Oct 2, 2009, at 2:38 AM, Arne wrote:
I would really enjoy that feature, too!
On 29 Sep., 20:17, Tom_E te.mli...@googlemail.com wrote:
Being able to selectmultiplefilesand then 'Ignore' all
That's something you set up for Subversion itself, and Versions will
respect it. Modify your ~/.subversion/config file by setting enable-
auto-props = yes and adding lines (under the [auto-props] section)
like the following:
*.html = svn:eol-style=native;svn:mime-type=text/html
*.jpg =
Notice that it crashes in libapr, which is used by Subversion. Perhaps
providing more information like the repository URL used would help.
BTW, booting to the 64-bit kernel is very unlikely to affect crashes —
the process will run as 32/64-bit regardless whether enabled or not.
- Quinn
.
- Quinn
On Oct 2, 2009, at 1:51 PM, mupdegraff wrote:
What do I need to do to get you more info on the repository URL?
On Oct 2, 1:42 pm, Quinn Taylor quinntay...@mac.com wrote:
Notice that it crashes in libapr, which is used by Subversion.
Perhaps
providing more information like
Bob -
I think we can all accept that some computers are never allowed to be
connected to the internet, and can understand the problem and
frustration you're feeling by not being able to register on such
machines. Don't assume that anyone was judging your *character* by
commenting about
My guess is that implementing something like this would (a) be tricky,
and (b) reduce performance. The reason I say that is because
repository checking is most likely run concurrently, and defining
groups that use the same account and password would require additional
overhead, and require
Same goes for modifications, naturally. An svn update will grab any
changes.
- Quinn
On Sep 20, 2009, at 9:21 AM, jo wrote:
Thanks Quinn,
but actually I'm not getting files added by others, only modified
files.
jo!
svn --version
svn, Version 1.6.2 (r37639)
On Sep 19, 11:12 pm, Quinn
By default, `svn update` updates your working copy (recursively) to
match whatever is in the repository. That means anything in the
directory or below it in the hierarchy. If resources are added or
removed within that directory, your working copy will be updated
accordingly. You can use
1 - 100 of 185 matches
Mail list logo
