From: Achim Gratz <Stromeko@Nexgo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] ob-sql.el: probably an extra paren
Date: Fri, 22 Mar 2013 08:01:30 +0100 [thread overview]
Message-ID: <kigvjo$dbe$1@ger.gmane.org> (raw)
In-Reply-To: <87ehf84osd.fsf@bzg.ath.cx>
Am 21.03.2013 18:59, schrieb Bastien:
> Please see my reply to Yagnesh.
>
> It clearly describes a situation where automatically running tests
> with a pre-push hook would be a problem.
You keep mentioning a pre-push-hook to be run on the developers machine.
However, the test would run on the server and determine whether to
accept the commit into the repo or not. All your further arguments seem
to be based on that misunderstanding, so I won't comment on them.
As for Travis CI: a website that shows absolutely nothing when
JavaScript is turned off? No, thanks.
Regards,
--
Achim.
(on the road :-)
next prev parent reply other threads:[~2013-03-22 7:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 2:54 [BUG] ob-sql.el: probably an extra paren Nick Dokos
2013-03-20 6:47 ` Bastien
2013-03-20 12:39 ` Sebastien Vauban
2013-03-20 13:47 ` Bastien
2013-03-21 8:28 ` Achim Gratz
2013-03-21 13:41 ` Bastien
2013-03-21 14:03 ` Nicolas Richard
2013-03-21 16:58 ` Yagnesh Raghava Yakkala
2013-03-21 17:31 ` Bastien
2013-03-21 18:40 ` tests with travis-ci (was: [BUG] ob-sql.el: probably an extra paren) Yagnesh Raghava Yakkala
2013-03-21 20:41 ` tests with travis-ci Bastien
2013-03-21 22:20 ` Yagnesh Raghava Yakkala
2013-03-22 7:56 ` Yann Hodique
2013-03-22 10:40 ` Yagnesh Raghava Yakkala
2013-03-31 19:07 ` Yann Hodique
2013-03-22 6:40 ` Andreas Röhler
2013-03-22 12:55 ` Nick Dokos
2013-03-22 13:07 ` Andreas Röhler
2013-03-21 17:38 ` [BUG] ob-sql.el: probably an extra paren Achim Gratz
2013-03-21 17:59 ` Bastien
2013-03-22 7:01 ` Achim Gratz [this message]
2013-03-22 7:36 ` Bastien
2013-03-22 7:59 ` Achim Gratz
2013-04-06 0:46 ` Bastien
2013-03-22 10:44 ` Yagnesh Raghava Yakkala
2013-03-21 8:37 ` Sebastien Vauban
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='kigvjo$dbe$1@ger.gmane.org' \
--to=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).