From: Eric Schulte <schulte.eric@gmail.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Modifications to enable test script to run with emacs-23 and emacs-22
Date: Mon, 26 Sep 2011 06:07:54 -0600 [thread overview]
Message-ID: <87d3eny09x.fsf@gmail.com> (raw)
In-Reply-To: <m2litdghm2.fsf@btinternet.com> (Martyn Jago's message of "Sun, 25 Sep 2011 09:18:29 +0100")
Martyn Jago <martyn.jago@btinternet.com> writes:
> Hi David
>
> David Maus <dmaus@ictsoc.de> writes:
>
>> Hi Eric,
>> Hi Martyn,
>>
>> At Tue, 20 Sep 2011 09:03:27 -0600,
>> Eric Schulte wrote:
>>>
>>> Applied, Thanks! -- Eric
>>
>> I noticed that newlines in the commit messages of patches by Martyn
>> are somehow messed up:
>>
>> ,----
>> | Modifications to enable test script to run with emacs-23 and
>> emacs-22 * testing/org-test.el: enable test script to run with
>> emacs-23 and emacs-22 * testing/lisp/test-org-exp.el: added org-ascii
>> requirement
>> `----
>
> I too have noticed this - I generate the commit message in magit and
> generate the patch with git format-patch, and at that point newlines
> still appear to be honoured here. I then attach the patch inline to
> gnus. Any solutions welcome.
>
Hmm, the problem could be on my end. I manually copy and paste inline
patches into files (I never found out how to write an inline attachment
to a file with gnus), so it is possible that I am breaking commit
messages during that step. I'll look more closely during the next
patch.
Cheers -- Eric
>
> Best, Martyn
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-09-26 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 7:59 [PATCH] Modifications to enable test script to run with emacs-23 and emacs-22 Martyn Jago
2011-09-20 15:03 ` Eric Schulte
2011-09-25 7:35 ` David Maus
2011-09-25 8:18 ` Martyn Jago
2011-09-26 12:07 ` Eric Schulte [this message]
2011-09-26 17:51 ` Achim Gratz
2011-09-28 0:37 ` Eric Schulte
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=87d3eny09x.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=martyn.jago@btinternet.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).