On Tue, 04 Oct 2022 13:51:57 +0100
Bram Moolenaar wrote:
> The patch format is one that includes all the information, also about
> deleted files and special character handling. Git diffs normally don't
> include that, you have to carefully specify what kind of diff it should
> create (probably
> 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
On Tue, 4 Oct 2022 08:20:37 +0200
Tony Mechelynck wrote:
> 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.
Oh wow. Didn't know
On Tue, Oct 4, 2022 at 8:20 AM Tony Mechelynck
wrote:
>
> On Tue, Oct 4, 2022 at 7:38 AM Enan Ajmain <3nan.ajm...@gmail.com> 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
On Tue, Oct 4, 2022 at 7:38 AM Enan Ajmain <3nan.ajm...@gmail.com> 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.
