30 Mar
2012
30 Mar
'12
4:03 p.m.
On Fri, 30 Mar 2012 15:51:59 -0400
Calvin Morrison <mutantturkey(a)gmail.com> wrote:
On 30 March 2012 15:50, Darrell Anderson
<humanreadable(a)yahoo.com>
wrote:
you can check when they were commited and by who using some git
foo :-P
BTW, I recommend gitk which is a good graphical viewer for GIT
repositories, for people who don't like cutting and pasting SHA1s :)
I agree
with David.
I don't see how anyone would use one without tdelibs, so you
might as well remove the files from accessibility.
I don't have a problem with removing cruft. Usually a Good Thing.
Just every time we see these things the bug tracker grows and I
feel us all sinking deeper. As you noted, where do we find the
time? :)
I consider this part of the cruft, along with old
vimrc files :-)
After searching the entire source tree, I concluded those vimrc and
config.log files are from somebody on the Trinity team.... :) My
clues are the vimrc files are exactly the same (same person) and
the config.log files all include references to /opt/trinity. I
don't use vim and I'm paranoid about working directly within the
source tree (I always make copies). I counted 16 config.log files
and three vimrc files. Not many. I'll purge them.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting