-----Original Message-----
From: Dave Grundgeiger [mailto:dave.grundgeiger@codenouveau.com]
Sent: Wednesday, February 14, 2007 3:42 PM
To: users@subversion.tigris.org
Subject: Re: rename and diff
> What is the accepted practice when you have a complicated set of
changes
> for which you want to create a single patch?
I haven't received any comments on this. *Is* there a standard practice?
It
seems fairly straightforward: I've issued a bunch of svn rename commands
in
my WC, but this can't be represented in a diff file. I want to hand over
a
convenient, atomic patch to a project's maintainers. What do others do?
My
solution was to supply a batch file with the svn commands, plus a diff
file
with the actual file changes. Is this reasonable?
Dave
Dave Grundgeiger
CodeNouveau, LLC
Develop .NET Software with Open-Source Tools
http://www.codenouveau.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
I'd like to know as well. We currently deliver patches by hand and our
customers are used to it. People don't seem very comfortable with just
replacing the system whole. We also have customers who modify the code
we distribute (I know a nightmare, we shouldn't be distributing code but
that's what we've always done). We're also concerned about SOX, though I
really think that as far as SOX compliance is concerned that's just a
red herring.
But, I digress, what is the best way to distribute patches to code where
the names can change?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 15 22:34:29 2007