tags 578762 + upstream thanks Hi Goswin,
Goswin von Brederlow wrote: > we had a discussion about the learning curve of git on irc and one > example was how a new user is supposed to find git-format-patch. He > would probably look at git-diff because that is the most similar thing > to other tools. It would be good if the git-diff manpage mentioned > git-format-patch, e.g. in a SEE ALSO section Yes, that’s a good idea. If you’d like to write a patch, the man pages are generated from files with names like git-diff.txt in the Documentation directory. Links between manual pages use markup like this: linkgit:git-format-patch[1]. To look at the result, you can make -C Documentation git-diff.1, with a config.mak in the toplevel directory like this: ASCIIDOC8=1 ASCIIDOC_NO_ROFF=1 Without those two settings, it should still work fine; the output will just have some .ft artifacts and so on. These settings are documented in the Makefile, and again in Documentation/Makefile. I would do it myself, but I am traveling today, just had a chance to look back over this. Thanks, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
