From: Boyd Lynn Gerber <gerberb@zenez.com>
To: Git List <git@vger.kernel.org>
Subject: Re: Future suggestion's to assist with changes to git.
Date: Thu, 28 Aug 2008 18:11:05 -0600 [thread overview]
Message-ID: <alpine.LNX.1.10.0808281801510.18129@suse104.zenez.com> (raw)
In-Reply-To: <7vej48d73e.fsf@gitster.siamese.dyndns.org>
On Thu, 28 Aug 2008, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>> 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.
>> - 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 <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
next prev parent reply other threads:[~2008-08-29 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 23:10 Future suggestion's to assist with changes to git Boyd Lynn Gerber
2008-08-28 23:30 ` Jeff King
2008-08-28 23:48 ` Boyd Lynn Gerber
2008-08-28 23:57 ` Jeff King
2008-08-29 6:50 ` Gerrit Pape
2008-08-28 23:59 ` Junio C Hamano
2008-08-29 0:06 ` Jeff King
2008-08-29 0:11 ` Boyd Lynn Gerber [this message]
2008-08-29 0:31 ` Perry Wagle
2008-08-29 0:50 ` Boyd Lynn Gerber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.1.10.0808281801510.18129@suse104.zenez.com \
--to=gerberb@zenez.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).