[issue9376] Refer to gnuwin32 diff util on development FAQ

Brian Curtin added the comment: "svn diff" is already explained a few times in the doc, including the line above the suggested change. -- resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue9376] Refer to gnuwin32 diff util on development FAQ

anatoly techtonik added the comment: > Brian Curtin added the comment: > > Until Rietveld has a defined place in our workflow, I don't think that's a > good idea. 1. AFAIK Python don't have any workflow. Do you speak about your own workflow? 2. What conditions should become True for you to th

[issue9376] Refer to gnuwin32 diff util on development FAQ

Mark Lawrence added the comment: I believe that the switch to mercurial is months if not years away, so I'd quite happily see just a reference to svn diff. Failing that I wouldn't loose any sleep over closing this, ok to leave it with you Brian? -- __

[issue9376] Refer to gnuwin32 diff util on development FAQ

Brian Curtin added the comment: Until Rietveld has a defined place in our workflow, I don't think that's a good idea. I think that will be a part of the process in the future, but we're not defining that here. -- ___ Python tracker

[issue9376] Refer to gnuwin32 diff util on development FAQ

anatoly techtonik added the comment: The better way would be > python -m easy_install review > python -m review -- ___ Python tracker ___

[issue9376] Refer to gnuwin32 diff util on development FAQ

Michael Foord added the comment: "svn diff" should be the one true way for creating patches, especially for windows users. This will all change when we switch to mercurial. -- nosy: +michael.foord ___ Python tracker

[issue9376] Refer to gnuwin32 diff util on development FAQ

Brian Curtin added the comment: I don't think we should have a list of three alternatives to the single way you really should be creating diffs. If you are working on Python you should have Subversion and run "svn diff", or have Mercurual and run "hg diff". I guess I'm -0 on this idea. I also

[issue9376] Refer to gnuwin32 diff util on development FAQ

anatoly techtonik added the comment: There is diff.py utility that is already available from standard Python distribution. -- nosy: +techtonik ___ Python tracker ___ ___

[issue9376] Refer to gnuwin32 diff util on development FAQ

New submission from Mark Lawrence : Section 6.1 How to make a patch? currently reads in part (a Windows version is available as part of the cygwin tools). I suggest that this is reworded to read (Windows versions are available as part of the cygwin tools or as part of the gnuwin32 project) I