This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ChangeLog entry complexity

From: Mike Frysinger <vapier at gentoo dot org>
To: libc-alpha at sourceware dot org
Cc: Allan McRae <allan at archlinux dot org>, Siddhesh Poyarekar <siddhesh at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, David Miller <davem at davemloft dot net>, normalperson at yhbt dot net, carlos at redhat dot com, pasky at ucw dot cz, roland at hack dot frob dot com, neleai at seznam dot cz
Date: Thu, 28 Mar 2013 23:26:12 -0400
Subject: Re: ChangeLog entry complexity
References: <Pine dot LNX dot 4 dot 64 dot 1303271427040 dot 23096 at digraph dot polyomino dot org dot uk> <20130328043009 dot GB17540 at spoyarek dot pnq dot redhat dot com> <5154F3AB dot 6030808 at archlinux dot org>

On Thursday 28 March 2013 21:51:39 Allan McRae wrote:
> The only thing that I will add is that I find it rather difficult to
> find the "why" of many changes - although it is better now that we
> enforce all but trivial patches to go via the mailing list, so there is
> some (although far from ideal) reference there.

ChangeLogs don't help with the why at all.  only the git commit message can do 
that.  i've been pushing my commits with standard info in them so `git log` is 
semi-useful.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

References:
- Re: ChangeLog entry complexity
  - From: Joseph S. Myers
- Re: ChangeLog entry complexity
  - From: Siddhesh Poyarekar
- Re: ChangeLog entry complexity
  - From: Allan McRae

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]