public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/6426] New: switch to "why this changed", not what changed Date: Thu, 17 Apr 2008 14:04:00 -0000 [thread overview] Message-ID: <20080417140353.6426.cagney@redhat.com> (raw) GNU coding standard dogma dictates that: - there shall be ChangeLog files - ChangeLogs contain "what changed" - source code contains "why it changed" or "why it is so" or "why it was" the idea motivating this is that developers read the source, and hence it is the source that should contain the detailed coding history; an the ChangeLog just lets you identify who changed what when. This all goes back to the days before revision control where often the only way to know who did what as through the ChangeLog file. With the introduction of distributed revision control that's less of a problem - change history can be identified by looking through your local copy of the entire repo. This of course begs the question, of should we drop ChangeLog files and rely more on GIT for recording what changed and by whom. The only stickler I know of is being able to properly record changes submitted by A but committed by B. -- Summary: switch to "why this changed", not what changed Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: cagney at redhat dot com OtherBugsDependingO 6423,6424 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=6426 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-04-17 14:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-17 14:04 cagney at redhat dot com [this message] 2008-04-25 18:05 ` [Bug general/6426] " pmachata at redhat dot com 2008-04-25 19:19 ` mark at klomp dot org
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=20080417140353.6426.cagney@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).