This is the mail archive of the 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

On Wed, Mar 27, 2013 at 05:28:34PM +0000, Joseph S. Myers wrote:
> Tarballs exist.  Version control systems other than git exist.  People 
> import software from one place to another, even if version control systems 
> other than git don't provide built-in equivalents of CVS vendor branches 
> (which were a very useful CVS feature).  People providing source code for 
> copyleft software on a device probably more often provide tarballs than 
> version-control repositories (in which case if they modified the code they 
> also need to provide some form of change log to meet requirements such as 
> "The work must carry prominent notices stating that you modified it, and 
> giving a relevant date." in GPLv3), and if they provide version-control 
> repositories they quite likely don't include upstream history.

I don't see how that makes a difference.  Even if those tarballs have
a ChangeLog file, it's rarely ever maintained.  I know that for Fedora
and downstream distributions (or for that matter Debian and
downstream) don't maintain the ChangeLog file for their backported
patches.  They have their own changelog section in either glibc.spec
or debian/changelog that describes the backported change.  Also, those
changelog entries are nothing like the GNU ChangeLog entries.  They're
typically just one-liners.

So whichever way you're looking at it, you always look at the upstream
baseline and the additional patches separately.  The only difference
removing a ChangeLog would have is that instead of reading into the
ChangeLog file to see what upstream changes happened, one checks out
the tag for that release in the upstream repository and plays with
git-log to see what changed and how and why.


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