all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Summarizing the purpose of a change.
Date: Sun, 22 Nov 2009 20:20:25 -0600	[thread overview]
Message-ID: <871vjq9e3a.fsf@red-bean.com> (raw)
In-Reply-To: <jwvskc657tb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 22 Nov 2009 20:53:02 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> So far, everyone who's chimed in has basically said "Yeah, I try to do
>> this".  But my question is more about making it policy, in the sense
>> that of making it appropriate to follow up to change saying "How about a
>> summary line for that?"
>
> We could try it.  I think adding such a summary line can be
> useful, indeed.  We could try to make it more of a convention, indeed.
> As somebody else pointed out, many VCS have special support for such
> "summary line".
> And after all, we already do the same for docstrings.
> Let's try it for a while,

Great.  I guess the way to do that is to follow up when we see it not
done and suggest it; if we're all happy with the results, we can
document the convention (where is the right place for that?)

-K




  reply	other threads:[~2009-11-23  2:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NBhoZ-0007oj-Uv@cvs.savannah.gnu.org>
2009-11-21  7:09 ` Summarizing the purpose of a change Karl Fogel
2009-11-21  8:07   ` Miles Bader
2009-11-21  9:11     ` Eli Zaretskii
2009-11-21 11:29       ` Giorgos Keramidas
2009-11-21 12:19   ` Alan Mackenzie
2009-11-21 12:43     ` Eli Zaretskii
2009-11-22 17:02       ` Karl Fogel
2009-11-23  1:53         ` Stefan Monnier
2009-11-23  2:20           ` Karl Fogel [this message]
2009-11-24 15:12             ` Thien-Thi Nguyen
2009-11-24 15:41               ` Alfred M. Szmidt
2009-11-25 21:02                 ` Richard Stallman
2009-11-26 20:20                   ` Thien-Thi Nguyen
2009-11-27  6:35                     ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vjq9e3a.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.