From: Jacob Sparre Andersen <jacob@jacob-sparre.dk>
Subject: Where to put change descriptions (Was: need help learning Ada for a modula-2 programmer)
Date: Thu, 30 Jan 2014 09:45:11 +0100
Date: 2014-01-30T09:45:11+01:00 [thread overview]
Message-ID: <87fvo5eu3s.fsf_-_@adaheads.sparre-andersen.dk> (raw)
In-Reply-To: lccket$oo1$1@speranza.aioe.org
Nasser M. Abbasi wrote:
> Dirk Heinrichs wrote:
>> agent@drrob1.com wrote:
>>> -- REVISION HISTORY
>> You should avoid putting the revision history _into_ your files. It's
>> the job of your version control system to handle this. Putting it
>> into the file increases the probability of getting merge conflicts.
> Revision history belongs to the source code itself. If you remove it
> and put it in some separate container such as a database, then you are
> stuck to having that database along side for ever, and it means no one
> can see the revisions made to the source code, unless they access and
> install some additional software and files.
It looks like we've found a case of two rather different schools of
thought. (Luckily we agree that it is good to document changes. ;-)
Once upon a time I kept revision histories in my source files, but the
way I did it (which looked rather a lot like <agent@drrob1.com>s
example), it didn't really add any value.
One reason that revision histories in source files don't make sense to
me is that I often make changes which impact more than one source file.
Which source file should I put that change description in? Should I
update it in parallel in all the source files I change as I work on the
change?
I agree that one should document the changes in a change (commit) as
early as possible. I usually do that by writing an issue describing
what I think I have to do and why I think I have to do it. Once the
issue is written, I start on the change. More or less in the order;
interface, tests, body (and finally; figuring out what went wrong).
As I already have documented beforehand where and why I want to go, it
is seldom hard to write a meaningful description of the change once I
have verified that it passes both regression tests and new tests.
Greetings,
Jacob
--
»But you have to be a bit wary of a ship that collects
snowflakes.« -- Diziet Sma
next prev parent reply other threads:[~2014-01-30 8:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:06 need help learning Ada for a modula-2 programmer agent
2014-01-28 1:33 ` adambeneschan
2014-01-28 1:52 ` Jeffrey Carter
2014-01-28 12:18 ` Brian Drummond
2014-02-02 2:47 ` agent
2014-02-02 6:09 ` Jeffrey Carter
2014-02-02 15:02 ` agent
2014-02-02 16:00 ` gautier_niouzes
2014-02-02 19:48 ` Jeffrey Carter
2014-02-03 8:24 ` Dmitry A. Kazakov
2014-02-02 17:18 ` Brian Drummond
2014-02-03 0:10 ` agent
2014-02-03 0:36 ` agent
2014-02-03 12:53 ` Brian Drummond
2014-01-28 22:51 ` Jerry
2014-01-29 12:15 ` Mike H
2014-01-29 20:41 ` Jacob Sparre Andersen
2014-01-29 23:52 ` Jeffrey Carter
2014-01-30 9:05 ` Jacob Sparre Andersen
2014-01-30 14:20 ` Mike H
2014-01-30 14:35 ` Bill Findlay
2014-01-30 15:40 ` Mike H
2014-01-30 23:39 ` Jeffrey Carter
2014-01-31 20:16 ` Mike H
2014-01-29 23:52 ` Jeffrey Carter
2014-01-30 1:44 ` Bill Findlay
2014-01-30 2:01 ` Jeffrey Carter
2014-01-30 12:24 ` Simon Wright
2014-01-30 23:38 ` Jeffrey Carter
2014-02-03 23:12 ` agent
2014-02-04 6:10 ` J-P. Rosen
2014-02-04 22:38 ` agent
2014-01-29 16:58 ` Dirk Heinrichs
2014-01-29 20:43 ` Randy Brukardt
2014-01-29 22:53 ` Georg Bauhaus
2014-01-30 12:13 ` Simon Wright
2014-01-30 17:05 ` Dirk Heinrichs
2014-01-30 23:21 ` Randy Brukardt
2014-01-30 4:29 ` Nasser M. Abbasi
2014-01-30 8:45 ` Jacob Sparre Andersen [this message]
2014-01-30 9:53 ` Georg Bauhaus
2014-01-30 21:58 ` Randy Brukardt
2014-01-30 16:28 ` Pascal Obry
2014-01-30 17:43 ` Marius Amado-Alves
2014-01-30 18:10 ` Simon Wright
2014-01-30 22:38 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox