Normally one would write in the top of the file you edit, who you are and
when you did what.
Sometimes thuogh, a solution spans several such files and piecing the logic
together can be a pain.
I propose therefore that we use TODO.txt (or perhaps a dedicated one for
this purpose) so we can explain a mutiple file edit with a single logical
explanation.
Just a heads up about where you'd be able to find an explanation for
seemingly unrelated edit events....
On Tuesday, March 12, 2019 6:25:20 AM EDT, Soren Bro wrote:
Normally one would write in the top of the file you edit, who you are and
when you did what.
Yes, that's about right.
Sometimes thuogh, a solution spans several such files and piecing the logic
together can be a pain.
This is what a "commit message" is for.
I propose therefore that we use TODO.txt (or perhaps a dedicated one for
this purpose) so we can explain a mutiple file edit with a single logical
explanation.
Denied. The best way to do this is when committing the code. When you do
an hg addremove; hg commit, Mercurial launches an editor, and that's where
you put a summary of your changes. This is actually very important and I'm
glad you brought it up. Nobody---and I do mean nobody---on this project is
irreplaceable.
Just a heads up about where you'd be able to find an explanation for
seemingly unrelated edit events....
Normally one would write in the top of the file you edit, who you are and
when you did what.
Sometimes thuogh, a solution spans several such files and piecing the logic
together can be a pain.
I propose therefore that we use TODO.txt (or perhaps a dedicated one for
this purpose) so we can explain a mutiple file edit with a single logical
explanation.
Just a heads up about where you'd be able to find an explanation for
seemingly unrelated edit events....
Regards.
Søren
On Tuesday, March 12, 2019 6:25:20 AM EDT, Soren Bro wrote:
Yes, that's about right.
This is what a "commit message" is for.
Denied. The best way to do this is when committing the code. When you do
an hg addremove; hg commit, Mercurial launches an editor, and that's where
you put a summary of your changes. This is actually very important and I'm
glad you brought it up. Nobody---and I do mean nobody---on this project is
irreplaceable.
Thanks.