From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [Accepted] Fix html export of footnotes with lists, tables, quotes, etc. Date: Wed, 23 Mar 2011 15:30:22 +0100 Message-ID: <871v1xgb9d.fsf@gnu.org> References: <20110323140858.3C438715E@myhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=33776 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q2P5W-0000ly-Kx for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 10:31:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q2P5E-0000as-IP for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 10:30:49 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:57593) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q2P5E-0000ac-BU for emacs-orgmode@gnu.org; Wed, 23 Mar 2011 10:30:48 -0400 Received: by eyh6 with SMTP id 6so2264617eyh.0 for ; Wed, 23 Mar 2011 07:30:47 -0700 (PDT) In-Reply-To: (Puneeth Chaganti's message of "Wed, 23 Mar 2011 19:51:44 +0530") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Puneeth Chaganti Cc: emacs-orgmode@gnu.org Hi Puneeth, Puneeth Chaganti 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