emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Minshall <minshall@umich.edu>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: [PATCH] Re: worg patch: R usage of :colnames for :results
Date: Mon, 27 Sep 2021 08:05:53 +0300	[thread overview]
Message-ID: <834901.1632719153@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Sun, 26 Sep 2021 22:03:57 +0200." <878rzj3xzm.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 188 bytes --]

Bastien,

> I'm not sure what you mean, can you elaborate?

if a picture is worth a thousand words, what's a patch worth?  :)

thanks for the pointer to the orgweb sources.

cheers, Greg


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-contribute.html-Suggest-PATCH-on-Subject-line-when-s.patch --]
[-- Type: text/x-diff, Size: 1500 bytes --]

From 2594db749de7ae5ec9400b4397b0ba21d9526c9b Mon Sep 17 00:00:00 2001
From: Greg Minshall <minshall@umich.edu>
Date: Mon, 27 Sep 2021 08:03:42 +0300
Subject: [PATCH] contribute.html: Suggest '[PATCH]' on Subject: line when
 submitting patches

contribute.org: Modify text.

Also pointer to X-Woof-Patch as an alternative.
---
 contribute.org | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/contribute.org b/contribute.org
index 41ef346..bad79e4 100644
--- a/contribute.org
+++ b/contribute.org
@@ -120,10 +120,13 @@ More formally,
 
 ** Sending patches
 
-Use ~git diff~ or ~git format-patch~ to generate the patch files and then
-include them in an email to [[mailto:emacs-orgmode@gnu.org][emacs-orgmode@gnu.org]] describing what
+Use ~git diff~ or ~git format-patch~ to generate the patch files and
+then include them in an email to [[mailto:emacs-orgmode@gnu.org][emacs-orgmode@gnu.org]] describing what
 you've done.  If you have configured git to use [[https://git-send-email.io/][send-email]], then you
-can use that.
+can use that.  If you are able to add the phrase =[PATCH]= to the
+beginning of the Subject: line of your e-mail, that will help to
+manage your submission.[fn:: Adding a [[https://github.com/bzg/woof]["X-Woof-Patch"]] header to your
+e-mail can also accomplish this.]
 
 If your mail has not appeared on [[https://list.orgmode.org/][the list]] after waiting at least 15
 minutes, it may have been flagged as spam by the robot email
-- 
2.32.0


  reply	other threads:[~2021-09-27  5:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 15:11 worg patch: R usage of :colnames for :results Greg Minshall
2021-09-26 15:17 ` Bastien
2021-09-26 18:17   ` Greg Minshall
2021-09-26 20:03     ` Bastien
2021-09-27  5:05       ` Greg Minshall [this message]
2021-09-27  5:26         ` [PATCH] " Bastien
2021-09-27  6:49           ` Greg Minshall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834901.1632719153@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).