From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Boyd Lynn Gerber <gerberb@zenez.com>, Git List <git@vger.kernel.org>
Subject: Re: Future suggestion's to assist with changes to git.
Date: Thu, 28 Aug 2008 20:06:15 -0400 [thread overview]
Message-ID: <20080829000615.GA30453@coredump.intra.peff.net> (raw)
In-Reply-To: <7vej48d73e.fsf@gitster.siamese.dyndns.org>
On Thu, Aug 28, 2008 at 04:59:17PM -0700, Junio C Hamano wrote:
> 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.
I think this can be generalized to "messages from the maintainer of your
systems". In the case of single-user installs, a message from the
package maintainer is appropriate. For a multi-user system, I would
expect a message from the admin to all of the users of the software.
> 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.
Personally, I would rather have my task succeed with a little extra spew
to stderr than to fail completely. And that would get the people who
were against the change involved in the discussion at a much earlier
point.
-Peff
next prev parent reply other threads:[~2008-08-29 0:07 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 [this message]
2008-08-29 0:11 ` Boyd Lynn Gerber
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=20080829000615.GA30453@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=gerberb@zenez.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).