> -----Original Message-----
> From: Andy Levy [mailto:andy.levy_at_gmail.com]
> Sent: Monday, August 03, 2009 1:18 PM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Feature Request: Option to *always* commit all the
changes in the
> *entire* working copy.
>
> On Mon, Aug 3, 2009 at 07:07, Nick Sabalausky<business4_at_semitwist.com>
wrote:
> > levyam Full name Andy Levy Date 2009-08-03 03:29:35 PDT Message On
Sun, Aug
> > 2, 2009
[snip]
> >
> > I have never had a working copy that included both changed files I
was ready
> > to commit and changed files I wasn't ready to commit. In fact, I
don't work
> > in such a way that that would ever happen.
>
> And I do all the time, because my change management process & timing
> requirements more or less require that I do so (otherwise I'd need to
> maintain a half-dozen WCs of a single project on my workstation). And
> I've never had any problems with Subversion or TSVN resulting from it.
> Every one of my commits has had exactly what I wanted and expected
> included in it, because I review what's being committed before I click
> OK.
I have this feature *most* of the time, but then I use the excellent
sparse checkout feature and so committing everything I have checked out
in my repo simply requires committing the top directory in the working
copy, if I want to.
I never checkout more than 1 WC from any repository now, which leaves me
with just the problem if I want to commit all changes from 2
repositories... nothing's ever easy is it :-) Though I wonder how the OP
will handle just this scenario?
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2379926
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-04 11:15:50 CEST