>
> Aren't there two completely different issues here ?
>
What I describe is possible way to avoid even necessity of picking files
for commit one by one. But it is just my vision of svn workflow. May be
this can be useful for someone.
> 2. Batch commit.
>
> If I've worked on some source files, and a related header, I want to
> commit them together.
>
> However, if the header is in a folder some distance from the sources, it
> is awkward to select them all for a single commit. The header may be in a
> common folder of headers, wherein are others that I don't want to commit.
>
> So the request here is to be able to select file(s) in one place to be
> queued, then to go to another place and commit both local and queued.
>
>
>
It is also questionable practice (my opinin only) to has modified files not
intended for commit. If it is postponed work - I create patch (or move
modification in branch) and revert modified files.
Also it is can be dangerous - compile and test code in one environment
(others headers in your example) but commit code which will be then
compiled and work in different environment (others headers will be not
modified)
So I do my best to not have parallel works in working copy which will be
commited separately.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3088628
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-09-17 14:27:22 CEST