From: "Bao Haojun" <baohaojun@gmail.com>
To: Bastien <bzg@altern.org>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: org-jira.el
Date: Thu, 05 Jan 2012 22:42:38 +0800 [thread overview]
Message-ID: <8739bu2otd.fsf@baohaojun.rayzertrack.com> (raw)
In-Reply-To: <874nwa1nan.fsf@gnu.org> (Bastien's message of "Thu, 05 Jan 2012 11:00:48 +0100")
Bastien <bzg@altern.org> writes:
> Nick Dokos <nicholas.dokos@hp.com> writes:
>
>> The current contrib/lisp/org-jira.el is pretty trivial: it just defines
>> a jira link type, so maybe it can be integrated into the new org-jira.el,
>> instead of having two of them lying around.
>
> Agreed. In the same vein, perhaps jira2.el and jira.el could be merged
> into one single library.
Agreed. I have not looked into org-mode source code yet, so do not know
about contrib/lisp/org-jira.el, but I think it is the same one on
emacswiki, which has been abandoned by its author. So, it will be
trivial to merge its functionality.
You are also right that jira2.el and jira.el can be merged,
theoretically. The jira2.el, as a library, is a superset of jira.el in
terms of functionality, since jira2.el uses soap, while jira.el uses
xml-rpc; and soap is better supported by jira than xml-rpc.
The difficulty lies in that jira.el is also a major mode (in addition to
providing the library for the major mode). To make sure backward
compatible will require some effort. Jira2.el, OTOH, has stopped to be a
major mode, and only provided library for (the new) org-jira.el.
Anyway, I will try to update jira.el and contact the original author to
see if he agrees.
next prev parent reply other threads:[~2012-01-05 14:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 12:08 org-jira.el Bao Haojun
2012-01-03 8:07 ` org-jira.el... and Org conventions (Bastien, Carsten and all) Sebastien Vauban
2012-01-03 15:53 ` Bao Haojun
2012-01-03 16:25 ` Sebastien Vauban
2012-01-03 16:28 ` Allen S. Rout
2012-01-04 16:47 ` Bastien
2012-01-04 17:13 ` Nick Dokos
2012-01-03 23:34 ` Standard property proposal (was: org-jira.el... and Org conventions (Bastien, Carsten and all)) Karl Voit
2012-01-04 16:50 ` Standard property proposal Bastien
2012-01-03 13:49 ` org-jira.el Marc Spitzer
2012-01-04 16:52 ` org-jira.el Bastien
2012-01-04 17:53 ` org-jira.el Nick Dokos
2012-01-05 10:00 ` org-jira.el Bastien
2012-01-05 14:42 ` Bao Haojun [this message]
2012-01-05 17:08 ` org-jira.el Jonathan Arkell
2012-01-06 0:32 ` org-jira.el Bao Haojun
2012-01-06 15:24 ` org-jira.el Bao Haojun
2012-01-04 18:36 ` org-jira.el Richard Riley
2012-01-04 19:49 ` org-jira.el Mehul Sanghvi
2012-01-05 10:01 ` org-jira.el Bastien
2012-01-05 15:42 ` org-jira.el OSiUX
2012-01-06 0:28 ` org-jira.el Bao Haojun
2012-01-06 15:54 ` org-jira.el Bao Haojun
2012-01-09 20:26 ` org-jira.el OSiUX
2012-01-10 2:40 ` org-jira.el Bao Haojun
-- strict thread matches above, loose matches on Subject: below --
2009-06-03 15:25 org-jira.el Jonathan Arkell
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=8739bu2otd.fsf@baohaojun.rayzertrack.com \
--to=baohaojun@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).