On Apr 17, 2006, at 2:10 PM, Ben Collins-Sussman wrote:
> Hi folks, it's been a while since I worked on subversion coding
> project. This is a proposal for a new client-side feature I'd like to
> work on. (For svn 1.5, obviously, not 1.4).
>
> It's vaguely based on a similar feature in perforce, and it's
> something a few of us have gotten used to since working at Google -- a
> nice convenience.
If you are going to go down this road, might I suggest borrowing a
bit of intelligence from Perforce's submit form.
I use Perforce at work. To be honest, I almost never use changelists
for files in progress because I don't need to. When I'm ready to
submit something, I issue a p4 submit. Here is an example of the
submit form (this will look familiar to perforce users):
Change: new
Client: jims_client_spec
User: correia
Status: new
Description:
<enter description here>
Files:
//depot/MyFancyProject/main.c # edit
//depot/MyFancyProject/unit_tests.c # edit
The small, but great feature here, is that if any files in the Files
section aren't ready to submit, or aren't logically part of this
change, you just delete them from the Files section and they aren't
submitted.
It would be great if svn ci at the root of a WC gave me a similar,
convenient way to do this. (I know I can do it today, in any number
of ways, but none of them feels as convenient as it is in perforce.)
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 18 02:00:05 2006