RE: Re: feature request: queue for commit

"questionable practice"

Maybe.

But this is the real world. Not everything happens according to anyone's version of "best practice".

All sorts of things can get in the way :

Mistakes.

Lapses in personal organization.

Requirement to build Debug versions of programs for testing with which won't get committed.

Urgent requests to work on some different files and commit them, while leaving half-finished work elsewhere.

Any of these can be avoided with care. And possibly with extra complete sandboxes. And possibly including development branches so work done in a sandbox with Debug builds can be committed to the branch then merged for further testing with Release builds.

All of this can seem a bit complicated in real life and may get skipped.

Or fixes committed and left for someone else to test.

And still doesn't completely make the original issue go away ......

The header and source may be vastly separated within the source tree and inconvenient (certainly not impossible) to select from a common point. It's just slightly more convenient to be able to visit the folder and pick a file(s) to be included in the commit done later from somewhere else.

I don't know that it is actually something I need to properly request for myself, just trying to show there are reasonable reasons why it might be useful.

Regards,

Richard.

[Blue line]
Richard Kerry
BNCS Engineer, SI SOL Telco & Media Vertical Practice
T: +44 (0)20 3618 2669
M: +44 (0)7812 325518
G300, Stadium House, Wood Lane, London, W12 7TA
richard.kerry_at_atos.net<mailto:richard.kerry_at_atos.net>

[Atos logo]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitt
________________________________
From: Sergey Azarkevich [azarkevich_at_gmail.com]
Sent: 17 September 2014 13:27
To: users_at_tortoisesvn.tigris.org
Subject: Re: Re: feature request: queue for commit

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.
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3088763

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-09-19 12:43:35 CEST