emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [patch] Don't output preamble DIV if its contents is empty
Date: Sat, 29 Oct 2011 21:28:55 +0200	[thread overview]
Message-ID: <80r51va96w.fsf@somewhere.org> (raw)
In-Reply-To: 87ipn8yqxu.fsf@gnu.org

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>>> are there adverse effects when an empty div is in the file?
>> Yes, there are, reason for such patch.
> I understand the reasons and I have applied the patch -- please provide a
> ChangeLog next time.

I can assure you that I'll do, as I just began doing...

> You can provide it like you just did (with the tag filter patch), but even
> better is to include the ChangeLog in the commit log, after the first line.
> Check available commits on http://orgmode.org/w/org-mode.git to get the
> idea.

OK. Understood.

Question: why do we do like that (inserting the ChangeLog contents after the
first line of the commit log)?  Is it automatically used somewhere to generate
a proper ChangeLog file?

Why isn't there a real shared ChangeLog file in the repository?

I want to know, because I want to learn more about all the aspects of this
project in particular, but as well collaborative work in general...

Best regards,

Sebastien Vauban

  reply	other threads:[~2011-10-29 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 19:58 [patch] Don't output preamble DIV if its contents is empty Sebastien Vauban
2011-10-09 11:24 ` Carsten Dominik
2011-10-09 18:34   ` Sebastien Vauban
2011-10-29 11:31     ` Bastien
2011-10-29 19:28       ` Sebastien Vauban [this message]
2011-10-30  0:12         ` Bastien

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:

  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=80r51va96w.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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


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).