[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Summarizing the purpose of a change.
From: |
Miles Bader |
Subject: |
Re: Summarizing the purpose of a change. |
Date: |
Sat, 21 Nov 2009 17:07:29 +0900 |
Karl Fogel <address@hidden> writes:
> In many projects, there is a convention of summarizing the purpose of a
> change in one or two sentences at the start of the log entry. This makes
> the rest of the log entry (and the change itself) easier to understand.
And if possible, make the summary not "1 or 2" sentences, but a single
not-to-long line, such as you'd use for an email Subject: header.
-Miles
--
The automobile has not merely taken over the street, it has dissolved the
living tissue of the city. Its appetite for space is absolutely insatiable;
moving and parked, it devours urban land, leaving the buildings as mere
islands of habitable space in a sea of dangerous and ugly traffic.
[James Marston Fitch, New York Times, 1 May 1960]
- Summarizing the purpose of a change., Karl Fogel, 2009/11/21
- Re: Summarizing the purpose of a change.,
Miles Bader <=
- Re: Summarizing the purpose of a change., Alan Mackenzie, 2009/11/21
- Re: Summarizing the purpose of a change., Eli Zaretskii, 2009/11/21
- Re: Summarizing the purpose of a change., Karl Fogel, 2009/11/22
- Re: Summarizing the purpose of a change., Stefan Monnier, 2009/11/22
- Re: Summarizing the purpose of a change., Karl Fogel, 2009/11/22
- Re: Summarizing the purpose of a change., Thien-Thi Nguyen, 2009/11/24
- Re: Summarizing the purpose of a change., Alfred M. Szmidt, 2009/11/24
- Re: Summarizing the purpose of a change., Richard Stallman, 2009/11/25