On Wed, Dec 21, 2011 at 12:10:26PM -0800, Randon Spackman wrote:
> One of my common use cases for subversion is to want to split my changes into
> two separate commits. In the past, I would do the following:
>
>
> 1) Check out
>
> 2) Make changes
>
> 3) Realize that this should
On Dec 21, 2011, at 14:10, Randon Spackman wrote:
> I’d like to see a new svn command such as “svn localize” (don’t keep my
> terminology if it sucks) that would make the directory you specify its own
> independent working copy that can be copied and manipulated individually,
This function has
On 12/21/2011 4:31 PM, Randon Spackman wrote:
Hmm... It's close, but the limitations on only assigning one per file
are a bit onerous; it's very often in the same file that I'm working
on that I find bugs, etc., that I want to commit separately.
Randon
Normally I have one "main" sandbox
ay, December 21, 2011 5:28 PM
To: Randon Spackman
Cc: users@subversion.apache.org
Subject: Re: Request for thoughts on working copy enhancement request
Randon,
On Wed, Dec 21, 2011 at 3:10 PM, Randon Spackman
mailto:randon.spack...@hotdocs.com>> wrote:
One of my common use cases for subversio
Sounds like a feature much like git's "git stash"
On 21 December 2011 20:10, Randon Spackman wrote:
> One of my common use cases for subversion is to want to split my changes
> into two separate commits. In the past, I would do the following:
>
>
>
> 1) Check out
>
> 2) Make changes
>
Randon,
On Wed, Dec 21, 2011 at 3:10 PM, Randon Spackman <
randon.spack...@hotdocs.com> wrote:
> One of my common use cases for subversion is to want to split my changes
> into two separate commits. In the past, I would do the following:
>
> ** **
>
> **1) **Check out
>
> **2)
One of my common use cases for subversion is to want to split my changes into
two separate commits. In the past, I would do the following:
1) Check out
2) Make changes
3) Realize that this should be more than one commit
4) Copy directory "MyCode" to "MyCode2"
5) Rev
