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 simply find it much easier to download and install these individual tools, e.g. I also have their version of grep which is vastly superior to Windows find

There is diff.py utility that is already available from standard Python distribution.

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 don't even know where the dev/faq page is located in SVN to make any potential change.

"svn diff" should be the one true way for creating patches, especially for windows users. This will all change when we switch to mercurial.

The better way would be
> python -m easy_install review
> python -m review

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.

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?

> Brian Curtin <curtin@acm.org> 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 think that's a good
idea? I.e. fill the blanks:
    if ... and ... and ...:
      debug("Rietveld has a defined place in out workflow")
      good_idea = True

"svn diff" is already explained a few times in the doc, including the line above the suggested change.