emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-orgmode@gnu.org
Subject: Re: A request: Moving away from ChangeLog
Date: Fri, 21 May 2010 15:47:31 +0200	[thread overview]
Message-ID: <87wruxicy4.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: 7D47FD95-8C8D-4540-864A-D2C76B998A52@gmail.com

John Wiegley <jwiegley@gmail.com> writes:

Hi John,

>   Line 1 is a <50 character short description
>
>   Line 3 starts a 72-column full commit entry, formatted just like a
>   ChangeLog entry, but without leading whitespace or '*'.  If a changed
>   file is mentioned, the mention isn't repeated by git-changelog; but
>   if it's not mentioned, it gets added automatically to the generated
>   ChangeLog.

I think it would be better if line 3+ would be exact ChangeLog entries
format-wise, so that you can still use emacs' ChangeLog facilities
(`add-change-log-entry').  I don't really want to write the changed file
and function names on my own, and adding them correctly is exactly what
that function does very well.

Bye,
Tassilo

  reply	other threads:[~2010-05-21 14:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21  9:06 A request: Moving away from ChangeLog John Wiegley
2010-05-21  9:41 ` John Wiegley
2010-05-21 12:15   ` Carsten Dominik
2010-05-21 12:50     ` John Wiegley
2010-05-21 13:47       ` Tassilo Horn [this message]
2010-05-21 15:06         ` John Wiegley
2010-05-21 15:39           ` Bernt Hansen
2010-05-21 15:46             ` John Wiegley
2010-05-21 16:01               ` Bernt Hansen
2010-05-21 16:32             ` Eric Schulte
2010-05-21 15:53           ` Carsten Dominik
2010-05-21 15:58             ` John Wiegley
2010-05-21 14:32       ` Carsten Dominik
2010-05-21 15:08         ` John Wiegley
2010-05-21 15:33         ` John Wiegley
2010-05-21 13:01     ` Ben Finney
2010-05-21 14:21       ` Carsten Dominik
2010-05-21 21:10 ` Christian Egli
2010-05-21 21:17   ` Julien Danjou
2010-06-01 14:58   ` Carsten Dominik
2010-06-02  7:44     ` Christian Egli
2010-06-02  9:32       ` Carsten Dominik

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=87wruxicy4.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=emacs-orgmode@gnu.org \
    /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).