From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: remote execution in heterogeneous environment Date: Thu, 20 Dec 2012 18:30:30 +0100 Message-ID: <871uekljgp.fsf@bzg.ath.cx> References: <6D36E0F9-01D1-4F95-9FAA-B2B2CA10E57E@gmail.com> <87623zaj4j.fsf@gmx.de> <87hang279z.fsf@gmx.de> <87d2y4oeys.fsf@bzg.ath.cx> <8738z0wtgi.fsf@Rainer.invalid> <87bodo1vtj.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52154) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tljx6-0006i1-By for emacs-orgmode@gnu.org; Thu, 20 Dec 2012 12:30:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tljx2-00043T-Qj for emacs-orgmode@gnu.org; Thu, 20 Dec 2012 12:30:36 -0500 Received: from mail-wg0-f44.google.com ([74.125.82.44]:55107) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tljx2-00043L-J6 for emacs-orgmode@gnu.org; Thu, 20 Dec 2012 12:30:32 -0500 Received: by mail-wg0-f44.google.com with SMTP id dr12so1658067wgb.35 for ; Thu, 20 Dec 2012 09:30:31 -0800 (PST) In-Reply-To: <87bodo1vtj.fsf@gmx.de> (Michael Albinus's message of "Thu, 20 Dec 2012 18:23:52 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Michael Albinus Cc: Achim Gratz , emacs-orgmode@gnu.org Hi Michael, thanks for offering your help! The first step is to clone the repository: ~$ git clone git://orgmode.org/org-mode.git You are in the master branch, the one we use for latest developments. The other branch is "maint", the one we use for bug fixing. The next version of Org, 7.9.3 will be released from maint, the next major version from master. >From the org-mode repo, simply run "make test": it will compile the files and run the test suite. To debug the tests, go to the "testing/" directory, load org-*.el files, then find the failing tests in testing/lisp/. Since there are many tests affected, my guess is that some top-level testing function (either in testing/ or testing/lisp) is not up to date. If you have any other question, let us know. Also, if you can send patches here first next time, that'd of *great* help! Best, -- Bastien