emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [patch] small fix to org.texi
Date: Sun, 13 Sep 2015 18:40:12 +0200	[thread overview]
Message-ID: <87fv2i46j7.fsf@gmx.us> (raw)
In-Reply-To: 20150913092953.09ca3ef3@gauss

Joe Riel <joer@san.rr.com> writes:

> Thanks for the notice. 
>
> I didn't see that when I first read it.  Hmm.  I posted two others
> yesterday.  What should I do now?  Edit the commit messages and
> post the patches?  Would the duplicate posts be an issue?

Thanks, I hadn't seen those patches.  Just reply to the mail with the
patches and attach the patch with updated commit message.

Since your git email suggests that you are associated with a major
software company, it's best if we follow the rules stringently.

Also, I believe there's a limit of 10 lines you can change without
copyright assignment.  Though you have only changed documentation, which
may or may not be within the same limit....  Anyway, it's not an issue
presently.  Hopefully somebody knows to what extend there's a difference
between documentation and code, if at all.

Thanks for the patches and sorry to be a bother.

Rasmus

-- 
One thing that is clear: it's all down hill from here 

  reply	other threads:[~2015-09-13 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 16:12 [patch] small fix to org.texi Joe Riel
2015-09-13 16:25 ` Rasmus
2015-09-13 16:29   ` Joe Riel
2015-09-13 16:40     ` Rasmus [this message]
2015-09-13 17:34       ` Joe Riel
2015-09-13 17:30 ` [patch] small fix to org.texi add TINYCHANGE Joe Riel
2015-09-13 18:25   ` Rasmus

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=87fv2i46j7.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).