Re: Future suggestion's to assist with changes to git.

On Thu, 28 Aug 2008, Junio C Hamano wrote:

Jeff King [off-list ref] writes:

quoted

    For people building from source, we have the Release Notes, but
    beyond that, I don't know where to put it (and I don't meant the web
    site is a bad place -- the more places the better, but there is no
    catch-all place).

That would help compared to doing nothing, but many people who complained
in the first thread (this is the third one, by the way) was k.org users
who used a machine somebody else installs the software for them.  Messages
during installation would not help those people.

Sorry, about that but I was starting to loose things with all the gigantic 
... thread.  I wanted to be able to see some things happen, from the long 
thread and felt that having the CC list as long as it was was not 
assisting in getting a resolution.

quoted

  - the command complaining that my use of it is deprecated. In
    retrospect, we probably should have done this.

This is arguable.  People would have get annoying messages thrown into
their mailbox from their cron jobs, even before the switchover happened,
which effectively means that we move the whining period from now back to
the beginning of the deprecation period -- it won't reduce the amount of
actual whining.

I prefered the way it was done.  I would have hated the messages in my 
cron jobs.  Some of my cronjobs have everything going to /dev/null  When I 
am unable to convice the project to eliminate things like the above, I am 
forced to /dev/null them to be able to use them in a way that is not to 
annoying for me.  I really liked the way things were done with the 
exception of maybe a bit better communication.  But there will always be 
whiners.  Just want an other way to emphazise that things are going to 
change.  Maybe it will stop a few.

Thanks again for the good work done by all in the community.

--
Boyd Gerber [off-list ref]
ZENEZ	1042 East Fort Union #135, Midvale Utah  84047