emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Samuel Loury <konubinix@gmail.com>
Cc: OrgMode ML <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Fix uncaught error when trying to open a link at point
Date: Sat, 16 Mar 2013 20:32:46 +0100	[thread overview]
Message-ID: <87ppyzqgwx.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87vc8r6tg8.fsf@gmail.com> (Samuel Loury's message of "Sat, 16 Mar 2013 20:22:15 +0100")

Hi Samuel,

Samuel Loury <konubinix@gmail.com> writes:

> Bastien <bzg@altern.org> writes:
>> No problem at all.  I decided to go and accept patches from people
>> that did not confirm they got the FSF papers because merging 8.0
>> into Emacs trunk is not likely to happen to soon... So.
> Good news, I got the confirmation that my "assignment/disclaimer process
> with the FSF is currently complete". I do not know however if I have to
> do something to prove that in order to submit patches to this mailing
> list.

Great.  Normally I should receive the confirmation myself, I will
ping the copyright clerk if I don't receive it in a week or so.

I have added you to the list -- welcome!

> I then propose in attachment a set of four tests testing the problem
> mentioned in this thread: the behavior of org-open-at-point in front of
> bracket links and plain links.

Applied, thanks.

PS: The test suite is not (yet) included in GNU Emacs, so there
is no need to provide an assignment for this, I will state this
in Org's README and in Worg.


      reply	other threads:[~2013-03-16 19:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22  8:42 [PATCH] Fix uncaught error when trying to open a link at point Samuel Loury
2012-11-28 12:53 ` Nicolas Goaziou
2012-12-20  8:41 ` Bastien
2013-01-04 11:39   ` Samuel Loury
2013-01-04 13:17     ` Samuel Loury
2013-01-04 16:18       ` Bastien
2013-01-14 10:35         ` Samuel Loury
2013-02-13 15:25       ` Bastien
2013-02-13 16:39         ` Samuel Loury
2013-02-13 16:49           ` Bastien
2013-03-16 19:22             ` Samuel Loury
2013-03-16 19:32               ` Bastien [this message]

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:

  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=87ppyzqgwx.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=konubinix@gmail.com \


* 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


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).