On Tue, Oct 4, 2022 at 7:38 AM Enan Ajmain <[email protected]> wrote: > > Bram sends patches in vim_dev ML. But it's not structured to directly > use with `git am`, is it? If that's correct, what's the reason for > using a different patch format? > > P.S. I am not gonna use the patch email. But my email client, Claws, > highlights the patch. In vim patch's case, it can't. That's why I > noticed the difference. > > -- > Enan
Bram's patches are in context diff (not unified context diff) format, one of the formats acceptable to the "patch" program, and once upon a time that was the program to be used when updating one's Vim source. Nowadays, most people who compile their own Vim use either a git clone of Bram's github master, or (like I do) a Mercurial clone of Christian's Mercurial public clone of Bram's git master (that Mercurial repository is located at http://hg.256bit.org/vim) and then the email patches are just a reminder that a new patchlevel has been published. Their contents are then not used directly. Best regards, Tony. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXvpXG7Mc-epmCTnwcvEx2eKs%2BjDMQrinYVCCy042cTX2Q%40mail.gmail.com.
