emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: Bastien Guerry <bzg@gnu.org>, Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Re: Fix info manual compilation
Date: Sun, 14 Apr 2013 09:41:53 +0200	[thread overview]
Message-ID: <8761zpa79a.fsf@gmail.com> (raw)
In-Reply-To: <20130414014552.GA3248@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Sun, 14 Apr 2013 03:45:52 +0200")

Hello,

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> On Sat, Apr 13, 2013 at 10:42:12PM +0200, Nicolas Goaziou wrote:
>> Hello,
>> 
>> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>> 
>> > The info manual does not compile because of a wrong next node entry in
>> > org.texi.  A fix is attached.
>> 
>> Thank you for the patch.
>> 
>> You need to add TINYCHANGE at the end of the commit message before I can
>> apply it.

> I actually signed the FSF papers quite a while back; just forgot to
> mention it on the list :-p.

I have applied the patch. Thanks again.

I admit I was surprised not to see you in the list of contributors who
have signed FSF papers.

> My assignment number is: RT704245. In the form I had mentioned
> I submitted changes to doc/org.texi so this patch should be covered.
> Do I need to send a copy of the assignment to the list? I have a scan
> of the assignment.

Bastien (Cc'ed) will tell you if he needs the scan.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-04-14  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 19:35 Fix info manual compilation Suvayu Ali
2013-04-13 20:42 ` Nicolas Goaziou
2013-04-14  1:45   ` Suvayu Ali
2013-04-14  7:41     ` Nicolas Goaziou [this message]
2013-04-14  9:44       ` Suvayu Ali
2013-04-14  8:34     ` Bastien
2013-04-14 10:05       ` Suvayu Ali
2013-04-14 10:09         ` Bastien

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=8761zpa79a.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    /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).