[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Commit netiquette.
From: |
Alfred M. Szmidt |
Subject: |
Re: Commit netiquette. |
Date: |
Tue, 23 Feb 2010 14:25:40 -0500 |
> ----------------
> 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.
>
> That seems overly forceful, emacs is not just by emacs developers, it
> is used by an immense number of people.
I don't think it should issue an error, but it should prompt the
user. This is similar to how message-mode prompts if you mess up
the mail headers, like having a bogus email address in the To:
header.
I think user interactive promopts should be keep to a minimum. Maybe
one could use font-lock, and just mark it visually.
- Re: Commit netiquette., (continued)
- Re: Commit netiquette., Alfred M. Szmidt, 2010/02/19
- Re: Commit netiquette., Juanma Barranquero, 2010/02/19
- Re: Commit netiquette., Alfred M. Szmidt, 2010/02/20
- Re: Commit netiquette., Miles Bader, 2010/02/20
- Re: Commit netiquette., Eli Zaretskii, 2010/02/20
- Re: Commit netiquette., Miles Bader, 2010/02/21
- Re: Commit netiquette., Eli Zaretskii, 2010/02/21
- Re: Commit netiquette., Stefan Monnier, 2010/02/23
- Re: Commit netiquette., Alfred M. Szmidt, 2010/02/23
- Re: Commit netiquette., Juanma Barranquero, 2010/02/20