emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Accepted] Fix html export of footnotes with lists, tables, quotes, etc.
Date: Wed, 23 Mar 2011 15:30:22 +0100	[thread overview]
Message-ID: <871v1xgb9d.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTim4yhEoXpzvCoGMMcBL1LxDXz1Cp+fuK0u1bn6M@mail.gmail.com> (Puneeth Chaganti's message of "Wed, 23 Mar 2011 19:51:44 +0530")

Hi Puneeth,

Puneeth Chaganti <punchagan@gmail.com> writes:

> But, it looks like the commit message doesn't get into patchwork or is
> it that Bastien changed my bad commit message?  My commit message also
> mentioned that src code blocks don't work, and it possibly because of
> new lines being inserted.  

Your commit message went to the patchwork and I cleaned it up, yes.

> Bastien, did you remove it because it was irrelevant?

I probably should have kept this information, sorry.  I prefered to 
have a commit message saying what the commit does and not what it does
not -- thinking another commit will come soon and complete it.

> If the commit message was changed because, Bastien didn't notice it,
> can someone tell me the right way to send patches?  

I noticed it, don't worry :)

> I just want to reduce Bastien's trouble and this is leading to
> duplication of work, as well.

Thanks a lot for that -- the best way to send patches/commits to the
list is by using the command "git send-email".  Otherwise, the message
of the email is taken as the commit message by patchwork, and that I
need to reedit a bit.  But any other way is okay too, as long as I have
the information.

Best,

-- 
 Bastien

  reply	other threads:[~2011-03-23 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 11:52 [PATCH] Fix html export of footnotes with lists, tables, quotes, etc Puneeth Chaganti
2011-03-23 14:08 ` [Accepted] " Bastien Guerry
2011-03-23 14:21   ` Puneeth Chaganti
2011-03-23 14:30     ` Bastien [this message]
2011-03-23 14:37       ` Puneeth Chaganti
2011-03-27 10:58 ` [PATCH] " Jambunathan K
2011-03-29  9:20   ` Puneeth Chaganti
2011-07-10 16:03     ` Jambunathan K

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=871v1xgb9d.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=punchagan@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).