emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Luis Anaya <papoanaya@hotmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] New items pushed in into Org Mode Github.
Date: Sat, 8 Sep 2012 13:31:39 -0400	[thread overview]
Message-ID: <BLU0-SMTP131EF002A02624751155FE7B7AE0@phx.gbl> (raw)
In-Reply-To: <87bohgigv4.fsf@gmail.com> (Jambunathan K.'s message of "Sat\, 08 Sep 2012 22\:36\:39 +0530")

Jambunathan K <kjambunathan@gmail.com> writes:
Hi:



> It is great that you are updating your sources and providing updates on
> new features in the mailing list.  It would be much better if you could
> maintain a .org file in Worg that demoes all the capabilities of
> org-e-groff exporter.

The org file for the exporter is up to date in terms of features. This
was a small fix that I needed to place and it did not created a change
in the documentation. (C'mon, I just removed a \n :) )

I should do that on the babel exports. It's on the todo list. 

> My only concern is that updates that you are providing is getting
> fragmented (and not consolidated) as the exporter is continuing to be
> improved and solidified.
>
> ps: Definitely not meant as a criticism.

No worries, your point and concern is well taken. I try to keep the code
current, I'm not saying that I will always succeed, but I least I try
to do it. 

Before I push anything into Org Mode Github I:

1. Check out the current code from Org Mode. 
2. Do a diff for changes. For instance, in this case I noticed that
"macro" was removed and I removed it accordingly on the new code. I 
need to do it for the ChangeLog (that I never get right anyway, but 
I try). 
3. Run regression test. I have an automated regression test script that I
run for changes. I got burned once, not to anybody's fault, it happened
and highlighted the need for having it. 

Is there something that you've noticed that I should address? 

(Now I'm curious...)
-- 
Luis Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo

  reply	other threads:[~2012-09-08 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08 16:10 [ANN] New items pushed in into Org Mode Github Luis Anaya
2012-09-08 17:06 ` Jambunathan K
2012-09-08 17:31   ` Luis Anaya [this message]
2012-09-08 18:54     ` Jambunathan K
2012-09-08 19:08       ` Eric Schulte
2012-09-09  2:36         ` Luis Anaya

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=BLU0-SMTP131EF002A02624751155FE7B7AE0@phx.gbl \
    --to=papoanaya@hotmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@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).