From: Nick Dokos <nicholas.dokos@hp.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: remote execution in heterogeneous environment
Date: Thu, 20 Dec 2012 12:09:20 -0500 [thread overview]
Message-ID: <7451.1356023360@alphaville> (raw)
In-Reply-To: Message from Achim Gratz <Stromeko@nexgo.de> of "Thu, 20 Dec 2012 17:59:09 +0100." <8738z0wtgi.fsf@Rainer.invalid>
Achim Gratz <Stromeko@nexgo.de> wrote:
> Bastien writes:
> > Michael Albinus <michael.albinus@gmx.de> writes:
> >
> >> The following patch I've committed to Emacs' trunk, it fixes the problem
> >> as far as I could test. Maybe somebody from the org maintainers could
> >> merge it into the org repository.
> >
> > I've already merged it in maint and master.
>
> Unfortunately it breaks testing, at least in batch mode. See my other
> posting about it.
>
>
Isn't ``make test'' standard procedure before a commit? If not, it should be.
Otherwise, why have a test suite?
Nick
next prev parent reply other threads:[~2012-12-20 17:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6D36E0F9-01D1-4F95-9FAA-B2B2CA10E57E@gmail.com>
2012-12-18 7:56 ` remote execution in heterogeneous environment Michael Albinus
2012-12-20 13:16 ` Michael Albinus
2012-12-20 16:39 ` Bastien
2012-12-20 16:59 ` Achim Gratz
2012-12-20 17:09 ` Nick Dokos [this message]
2012-12-20 17:15 ` Bastien
2012-12-20 17:12 ` Bastien
2012-12-20 20:25 ` Achim Gratz
2012-12-20 17:23 ` Michael Albinus
2012-12-20 17:30 ` Bastien
2012-12-21 8:24 ` Michael Albinus
2012-12-21 8:51 ` Bastien
2012-12-21 17:32 ` Nick Dokos
2012-12-21 1:21 ` George Jones
2012-12-21 8:27 ` Michael Albinus
2012-12-22 13:32 ` George
2012-12-22 13:36 ` George
2012-12-22 13:48 ` Michael Albinus
[not found] ` <CAOhM7yVOvrL0F8v1hAnxb4z0Mw0kTf6L6_uZk5o7T3W08geUeg@mail.gmail.com>
[not found] ` <CAOhM7yXmD3OEhBt66Ts9YG+8s9LKhkw0-BT0grh734fH07p2pw@mail.gmail.com>
2012-12-23 14:10 ` Michael Albinus
2012-12-23 15:14 ` Bastien
2012-12-23 16:09 ` Michael Albinus
2012-12-23 16:47 ` Bastien
2012-12-23 17:53 ` George Jones
2012-12-23 19:54 ` Bastien
2012-12-23 21:37 ` George Jones
2012-12-24 13:38 ` Michael Albinus
2013-01-07 16:44 ` [BUG] " Achim Gratz
2013-01-08 8:36 ` Michael Albinus
2013-01-08 17:30 ` Achim Gratz
2013-01-08 18:02 ` Eric Schulte
2013-01-08 21:11 ` Michael Albinus
2013-01-09 7:31 ` Achim Gratz
2013-01-09 8:16 ` Michael Albinus
2013-01-09 11:49 ` Bastien
2013-01-09 13:05 ` Michael Albinus
2013-01-09 13:11 ` Bastien
2012-11-29 16:48 Neil Best
2012-11-29 17:05 ` Nick Dokos
2012-11-29 17:16 ` Nick Dokos
2012-11-29 21:48 ` Neil Best
[not found] ` <CANVU8H2wkXN90W+C24t75TDVEctGLqYOYi-H7e86_a2OkFFO8Q@mail.gmail.com>
[not found] ` <11047.1354217134@alphaville>
2012-11-29 22:07 ` Neil Best
2012-11-30 7:37 ` Michael Albinus
2012-11-30 15:33 ` Nick Dokos
2012-11-30 17:12 ` Michael Albinus
2012-11-30 18:24 ` Nick Dokos
2012-11-30 19:13 ` Michael Albinus
2012-11-30 18:02 ` Neil Best
2012-11-30 19:22 ` Michael Albinus
2012-11-30 20:13 ` Neil Best
2012-12-01 9:49 ` Michael Albinus
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=7451.1356023360@alphaville \
--to=nicholas.dokos@hp.com \
--cc=Stromeko@nexgo.de \
--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).