git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
BGBoyd Lynn Gerber <gerberb@zenez.com>
Date
Aug 29, 2008, 00:11 UTC
Message-ID
<alpine.LNX.1.10.0808281801510.18129@suse104.zenez.com>
In-Reply-To
<7vej48d73e.fsf@gitster.siamese.dyndns.org>
On Thu, 28 Aug 2008, Junio C Hamano wrote:
Show 10 quoted lines
> 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.

Show 9 quoted lines
>>   - 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

Previous: Jeff KingNext: Perry Wagle
Message 8 of 10 in “Future suggestion's to assist with changes to git.”
  1. Boyd Lynn GerberAug 28, 2008
  2. Jeff KingAug 28, 2008
  3. Boyd Lynn GerberAug 28, 2008
  4. Jeff KingAug 28, 2008
  5. Gerrit PapeAug 29, 2008
  6. Junio C HamanoAug 28, 2008
  7. Jeff KingAug 29, 2008
  8. Boyd Lynn GerberAug 29, 2008
  9. Perry WagleAug 29, 2008
  10. Boyd Lynn GerberAug 29, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.