----- Original Message ----
> From: Gale Andrews <
[hidden email]>
> | From Ed Musgrove
> > I started there in the first place. DiffUtils and xfdiff are both GnuWin--that
> is
> > what I used to create the patch you did not like. I used it just as specified
> on the above
> > mentioned Wiki.
>
> It was not that I didn't like it, it wasn't usable (in any automatic
> way) or clear what was changing (if trying to apply it manually).
I am sorry about the poor choice of words, "didn't like" was as close as I
could come as your original rejection was not sufficiently detailed for me
to come up with a more exact term <grin>.
Please commit this patch when and if appropriate; thank you!
The original patch you rejected was created with GNUWin diff using this process:
*copy OLDProject.cpp and NEWProject.cpp into the folder containing GNUWin
*open the CLI and make the current directory the folder containing GNUWin
*command: diff -u OLDProject.cpp NEWProject.cpp > outputFile.txt
outputFile.cpp is the file I attached which he did not like. I was trying the
GnuWin32 version of diff because Markus was less than happy with the Python
output. The Python output was created using the exact same steps (only using
the Python folder) and that is the one that you liked. Unfortunately, the current
version of Python 3.1 which I am using does not do recursion (-r switch) so it will
not do a diff on the Audacity source.
> As Markus said though, when you have a patch that applies
> changes to large numbers of files we really want one patch,
> not one patch per file.
Searching the Internet, I found out why WinCVS was refusing to acknowledge my
version of Python 3.1 -- it is hardcoded to only work with Python 2.4. I searched
my hard drives and found PFrank was using the python24.dll so I pointed WinCVS
at that library and it liked it.
Sometime in the near future I will test both the python 3.1 diff utility and the WinCVS
to see if they will do a unified diff on the entire Audacity source. If successful, I will
impose on you (unless you demure) to examine the output to see if either is acceptable.
-Ed Musgrove
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
