This. 1000 times this.
Don't clutter your source code with this kind of stuff. It'll just
cause you pain down the road. (Say, when merging two branches.)
// ben
On Wed, Aug 3, 2011 at 23:36, Sean Corfield <seancorfi...@gmail.com> wrote:
> I think Joop meant to use the change history in your version control system
> directly, rather than try to put it into the source code.
> I think the prevailing best practices these days are to _not_ duplicate
> change history into source code, even thru VCS keyword substitution. The
> change history is available in the VCS already and also in your IDE, so
> anyone who needs to know how a given file has changed can go look that up.
> Sean
> On Wed, Aug 3, 2011 at 12:29 PM, octopusgrabbus <octopusgrab...@gmail.com>
> wrote:
>>
>> Is there a preferred method for adding a Change History block to a
>> Clojure module? I'm doing this for now:
>>
>> (ns addr-verify
>> ^{:author "Charles M. Norton",
>> :doc "addr-verify is a small Clojure program that runs address
>> verification through ...
>>
>> Created on August 3, 2011
>> Change History: "}
>> (:gen-class)
>>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with your
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
