Returned mail: User unknown

2003-06-19 Thread Mail Delivery Subsystem
The original message was received at Thu, 19 Jun 2003 17:07:08 -0400 (EDT) from rly-xi01.mail.aol.com [172.20.116.6] *** ATTENTION *** Your e-mail is being returned to you because there was a problem with its delivery. The address which was undeliverable is listed in the section labeled: "-

Re: Is a ChangeLog file realistic if /lots/ of developers adding/lots/ of changes?

2003-06-19 Thread Thien-Thi Nguyen
[EMAIL PROTECTED]: If you have any advice or ways to streamline the process I would very much like to hear it. spend one hour a week as a group reading change logs (and only change logs -- no code!) for the week preceding. discuss applicability of changes, especially whether or not the

Re: Is a ChangeLog file realistic if /lots/ of developers adding/lots/ of changes?

2003-06-19 Thread Ronald Landheer-Cieslak
Changelogs are *not* a lot of work: they *save* a lot of work! Just my personal opinion, of course, but this is how *I* work: 1. make changes 2. diff with current CVS > patch 3. read patch and write the changelog for the patch 4. attach patch to the changelog and save it in my personal patch archi

Delivery Status Notification (Failure)

2003-06-19 Thread postmaster
This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed. [EMAIL PROTECTED] Reporting-MTA: dns;udcexbh02.us.trendnet.org Received-From-MTA: dns;udcintlab01.udc.trendmicro.com Arrival-Date: Thu, 19 Jun 2003 02:37:18 -0700 Final-Recipie

Re: Is a ChangeLog file realistic if /lots/ of developers adding/lots/ of changes?

2003-06-19 Thread Paul Eggert
[EMAIL PROTECTED] writes: > I want to follow correct GNU style but this ChangeLog file just seems like > too much work. Doesn't everyone agree? No. ChangeLogs take work, but it's generally useful work if done right. I often refer to ChangeLogs to figure out what happened and why. You don't want