Kyle Meyer writes:
>> Up to now I thought only a 'format-patch' can be applied easily. Would
>> you please share a way to apply an inline patch? Or at least give a hint?
>
> Sure. For an inline patch, you feed the entire message, rather than the
> attachment, to 'git am'. It looks like Gnus is
Marco Wahl writes:
> Up to now I thought only a 'format-patch' can be applied easily. Would
> you please share a way to apply an inline patch? Or at least give a hint?
Sure. For an inline patch, you feed the entire message, rather than the
attachment, to 'git am'. It looks like Gnus is your
Hi Kyle and Arun,
>> To make the handling of patches easier please use "format-patch".
>
> It looks like this was sent with git-send-email (which is fed
> format-patch output either explicitly or underneath), and it applied
> cleanly for me.
Okay, good. Thanks for sharing!
Apologies for
>> To make the handling of patches easier please use "format-patch".
>
> It looks like this was sent with git-send-email (which is fed
> format-patch output either explicitly or underneath), and it applied
> cleanly for me.
>
> My understanding is that, even though this project accepts patches as
Hi Marco,
Marco Wahl writes:
> To make the handling of patches easier please use "format-patch".
It looks like this was sent with git-send-email (which is fed
format-patch output either explicitly or underneath), and it applied
cleanly for me.
My understanding is that, even though this project
Hi Arun,
Thanks for the patch. I applied it.
> * doc/org-manual.org (Clocking Work Time): Replace "to that you can"
> with "so that you can".
To make the handling of patches easier please use "format-patch". More
details from the Emacs CONTRIB:
--8<---cut
* doc/org-manual.org (Clocking Work Time): Replace "to that you can"
with "so that you can".
---
doc/org-manual.org | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index b14c28807..b61644626 100644
--- a/doc/org-manual.org
+++
