From: Karl Fogel <kfogel@red-bean.com>
To: "T.V. Raman" <tv.raman.tv@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
"Juanma Barranquero" <lekktu@gmail.com>,
ams@gnu.org, "Stefan Monnier" <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: ChangeLogs on CVS? Commit netiquette.
Date: Thu, 18 Feb 2010 16:38:12 -0500 [thread overview]
Message-ID: <87eiki443f.fsf@red-bean.com> (raw)
In-Reply-To: <5f0ff9221002181207v3244055ax3b3223833a901609@mail.gmail.com> (T. V. Raman's message of "Thu, 18 Feb 2010 12:07:01 -0800")
"T.V. Raman" <tv.raman.tv@gmail.com> writes:
>My cvs snapshot of emacs has Changelog files only upto the end of
>2009 --- has the repository moved, or are there just no
>changelogs any more?
Hi, T.V.! Emacs switched to Bazaar. Please see
http://www.emacswiki.org/emacs/BzrForEmacsDevs
and ask any questions here, of course.
Best,
-Karl
>On 2/18/10, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>>> This seems more of a short comming in `bzr log --short' than in the
>>>> way one writes commit messages.
>>
>> Not really: it's the whole idea behing "bzr log --short".
>>
>>> We currently *have* policies about ChangeLog entries and commit logs,
>>> so I agree with Óscar: it is a good practice and we should require
>>> people to follow it; and treat people who doesn't the same way we
>>> treat people who mangles ChangeLog entries (that is, a gentle but firm
>>> reminder that we have guideliness and we're all expected to follow
>>> them).
>>
>> Yes, please, we should require the first line of commit messages to be
>> an acceptable summary of the whole changeset.
>>
>> Could someone update log-edit-mode's font-lock patterns so that the
>> first line is highlighted specially (at least in the Bzr and Arch
>> cases)?
>>
>> I think log-edit-mode should even go further in this direction.
>> The buffer should be created as
>>
>> ----------------
>> Author:
>> Summary:
>>
>> blablabla
>> ----------------
>>
>> where <blablabla> is the text taken from the ChangeLog. Then for
>> backends which support the notion of summary-line, C-c C-c could just
>> signal an error if the Summary line is still blank.
>> After that, empty header entries will get removed and the text is passed
>> as-is to the backend who is then free to pass it as-is to the underlying
>> VCS or to extract the various fields and do whatever it feels like
>> with them.
>>
>>
>> Stefan
>>
>>
>>
next prev parent reply other threads:[~2010-02-18 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 20:07 ChangeLogs on CVS? Commit netiquette T.V. Raman
2010-02-18 21:38 ` Karl Fogel [this message]
2010-02-19 0:18 ` T.V. Raman
2010-02-19 0:21 ` T.V. Raman
2010-02-19 0:44 ` Óscar Fuentes
2010-02-19 3:10 ` T.V. Raman
2010-02-19 3:20 ` T.V. Raman
2010-02-19 5:50 ` Karl Fogel
2010-02-19 7:16 ` Jan Djärv
2010-02-19 11:06 ` Andreas Schwab
2010-02-19 16:18 ` T.V. Raman
2010-02-19 16:34 ` Eli Zaretskii
2010-02-19 17:08 ` David Kastrup
2010-02-19 16:19 ` T.V. Raman
2010-02-19 18:21 ` Stefan Monnier
2010-02-19 20:56 ` David Kastrup
2010-02-23 16:21 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eiki443f.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=ofv@wanadoo.es \
--cc=tv.raman.tv@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.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).