Hello,
Am 18.11.2013 10:20, schrieb Dee Tooké:
> This sounds promising. I've currently got the top level folder
> checked out. Underneath that top level, there are (currently) about
> 100 sub-directories, each of which has an average of 6 further
> sub-directories. Looking roughly something like this:
>
> -Product Name
> --doc
> --src
> ---severalsubs in src
> ---assets
> --other1
> --other2
>
> So, none of the documentation is in the same directory as the source,
> but included within the src directories are other files that do come
> under the title/meaning of src, but simply aren't files I want to
> get. Similarly, in the documentation folders I might want to get
> .html and .pdf files, but I don't want demo videos or photoshop psd
> files etc.
The way I would probably handle such a situation is do the first
checkout at depth 1 (so that I only see see all the products), and then
when working on a product the first time, checkout the parts of it I'd
want to work on. This of course assumes that I'm always connected to the
repository and do not work offline.
If the structure of the folders is similar inside the products, another
option might be some scripting to automatically include/exclude the same
kind of directories in each of the directories so that you have already
checked out most things you need for all projects (you'd have to re-run
the script when a new product is added, though).
There are language bindings for most programming languages available
(but I think JavaScript is not among them) that make it easy to
enumerate the working copy or the repository and perform actions based
on the results, but that would be off-topic on this mailing list.
> Each time I do a new update (which will be at the top level folder),
> I'm expecting some files to have been changes, some to have been
> added/deleted, and some brand new folders.
If the depths are set correctly, updates and deletions are automatically
handled; additions depend on the update depth of the parent folder.
> I'm hoping to do one single update, but I understand I might have to
> do 5 or 6 updates (one for each of the filetypes I want).
>
> Does anyone know why in the check repository dialog that was working
> in 1.5, you can highlight one single file and right-click it and get
> it to check-out/update, but if you highlight more than one and try
> the same thing, you just get a bunch of "Skipped" messages.
As for me (and I think for most of the SVN community) performing an
update from the log, commit, or check repository window is an action
that is frowned upon and only performed in rare circumstances (like if
you try to find a regression or if you have a change in part A and you
know an unrelated change in part B will create conflicts right now but
no longer when some colleague has committed his part) because it will
often result in a mixed-revision working copy (and your colleagues might
get upset if you commit something that effectively breaks the build but
worked in your mixed-revision environment), I don't really know the
inner workings of those functionality, sorry (And I never ran into the
situation where I wanted to update more than one file or folder that
way, yet).
Regards,
Michael
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3068754
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-11-18 18:51:55 CET