> If someone has a good idea for a patch, then > git-format-patch/git-send-email them to the list for review and > application.
Of course, using the "Patches tracker" on the SF site is also a good alternative. https://sourceforge.net/tracker/?group_id=52322&atid=466458 Patches can be uploaded, commented on, and eventually accepted (and committed) through the web interface. I am a bigger fan of the old-fashioned mailing list interface (i.e., using 'git send-email' to post a message with "[PATCH]" in the subject to the mailing list where it can be publicly viewed and scrutinized and announced -- that's how the Git development team does it); however, SF has a history of doing these things through a tracked web interface. --Ted -- Ted Pavlic <t...@tedpavlic.com> ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
