emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Yagnesh Raghava Yakkala <hi@yagnesh.org>
Cc: Achim Gratz <Stromeko@Nexgo.DE>, emacs-orgmode@gnu.org
Subject: Re: [BUG] ob-sql.el: probably an extra paren
Date: Thu, 21 Mar 2013 18:31:33 +0100	[thread overview]
Message-ID: <87vc8k4q2y.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87hak4d712.fsf@yagnesh.org> (Yagnesh Raghava Yakkala's message of "Fri, 22 Mar 2013 01:58:17 +0900")

Hello Yagnesh,

Yagnesh Raghava Yakkala <hi@yagnesh.org> writes:

> We can use travis-ci for automated tests, I just run tests for org-mode¹ on travis
> with emacs-snapshot. Magit has been setup recently to run tests for multiple
> emacs versions² (emacs23, emacs24 and snapshot). travis has a facility to send
> mails if a test fails. 

Great!

> I see you have org-mode repo on your github account, all we need to do put a
> post recieve hook to mirror org-mode repo to github.
>
> we can adopt magit script³ to org-mode as it won't be synced to emacs
> trunk.
>
> what do you think?

I think this would be *fantastic*.  I have no time for this at the
moment, but anyone willing to help setting this up would be my hero.

Really :)

This is efficient and not intrusive.

To give another argument about why I think a pre-push hook on the
developer's side is wrong, imagine this scenario:

- developer A pushes a commit, all tests pass
- developer B works on latest HEAD assuming all tests pass
- he wants to push his commits but the tests fail
- he naturally thinks it's a problem with *his* changes
- ... but it is not ...
- M-x doctor RET

This happened for real: recently some tests passed under Emacs <24.3
but failed under Emacs >=24.3.  If we had a pre-push hook, I would not
even be able to push the fix, I would have to deactive the hook first.

Best,

-- 
 Bastien

  reply	other threads:[~2013-03-21 17:31 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 [this message]
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
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=87vc8k4q2y.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=Stromeko@Nexgo.DE \
    --cc=emacs-orgmode@gnu.org \
    --cc=hi@yagnesh.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).