emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Ista Zahn <istazahn@gmail.com>
Cc: "G. Jay Kerns" <gjkerns@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>,
	brendan.halpin@ul.ie, Eric Schulte <schulte.eric@gmail.com>
Subject: Re: Enabling another language in org-babel
Date: Mon, 28 Jul 2014 15:20:09 +0200	[thread overview]
Message-ID: <878und1jm8.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CA+vqiLGx7aE5ZnRz2-5wCnso0vKFYnNXOSxTDos8LD16uCd_Bw@mail.gmail.com>	(Ista Zahn's message of "Wed, 25 Jun 2014 09:44:29 -0400")

Hi Ista,

Ista Zahn <istazahn@gmail.com> writes:

> I don't know if this is ready for contrib yet (though I don't object
> if you think it is). I'm not sure what quality standards exist for
> contrib, but this is really quick and dirty; it would be nice to at
> least implement graphics support. On the other hand its better than
> nothing, so maybe it does make sense to add it to contrib.

Yes, it makes sense to add it to contrib, it will help others step up
and improve the code if needed.

> Also I'm not sure what the development process is once things go in
> contrib (sorry for my ignorance!). Does contrib live in the same code
> repository as the rest of org, or are things in contrib developed
> separately and pulled in later?

contrib/ lives in the same Git repository than the rest of Org (which
is arguably a problem).  So everything is developed at the same place.

Once you send me your public key, I'll grant you write access to the
repository and you can push commits.

> In short feel free to add it to contrib if you want, but be aware that
> it is  in pretty rough shape.

Please provide a separate commit on the list for this piece of code,
so that we can review it and commit it.  And if you want to get push
access, please send me your public key.

Thanks!

-- 
 Bastien

  reply	other threads:[~2014-07-28 17:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  8:54 Enabling another language in org-babel Brendan Halpin
2014-06-24 11:02 ` Eric Schulte
2014-06-24 12:05   ` Rainer M Krug
2014-06-24 19:52     ` Ista Zahn
2014-06-24 20:13       ` G. Jay Kerns
2014-06-25  8:33       ` Bastien
2014-06-25 13:44         ` Ista Zahn
2014-07-28 13:20           ` Bastien [this message]
2014-07-28 21:29             ` Ista Zahn
2014-07-29 14:36               ` Bastien
2014-07-30 16:47                 ` Ista Zahn
2014-07-30 17:06                   ` Nick Dokos
2014-07-30 17:16                   ` Achim Gratz
2014-07-31  0:23                   ` Jay Kerns
2014-07-31 10:52                   ` Bastien
2014-07-31 11:06                     ` Ista Zahn
2015-01-31 19:42                   ` Esa Palosaari
2015-01-31 19:50                     ` Esa Palosaari

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=878und1jm8.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=brendan.halpin@ul.ie \
    --cc=emacs-orgmode@gnu.org \
    --cc=gjkerns@gmail.com \
    --cc=istazahn@gmail.com \
    --cc=schulte.eric@gmail.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).