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

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 18, 2017, 14:41 UTC
Message-ID
<alpine.DEB.2.21.1.1709181637420.219280@virtualbox>
In-Reply-To
<xmqq377nwtbe.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Sat, 16 Sep 2017, Junio C Hamano wrote:
> And as you alluded to, we may need to see if we can help making it
> easier to do the latter when needed.
That mistakes it for "Someone Else's Problem".
Show 7 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > That's what you are buying into by having these "What's cooking" mails
> > that are in no usable way connected to the original threads.
> 
> For the above reason, I do not think this is a particularly useful
> stance to take.
I agree, but this is the process you chose to use.
Show 6 quoted lines
> Do you have a concrete suggestion to make these individual entries more
> helpful for people who may want go back to the original thread in doing
> so?  In-reply-to: or References: fields of the "What's cooking" report
> would not help.  I often have the message IDs that made/helped me make
> these individual comments in the description; they alone would not react
> to mouse clicks, though.
Oh gawd, not even more stuff piled onto the mail format. Please stop.
Show 5 quoted lines
> Having said that, I'd expect that individual contributors have past
> messages pertaining to the smaller numbers of their own topics in flight
> in their mailbox than the project wide "What's cooking" report covers,
> so perhaps an affort to devise such a mechanism may result in an
> over-engineering waste nobody finds useful.  I dunno.

I frequently find myself putting off that What's cooking mail because it simply takes too long to study.

It probably tries to serve too many purposes at the same time, and thereby none.

In the same vein as "to a hammer, everything looks like a nail": when it comes to project management, a dedicated tool will always beat a general-purpose mailing list.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 16 in “What's cooking in git.git (Aug 2017, #05; Tue, 22)”
  1. Junio C HamanoAug 22, 2017
  2. Brandon WilliamsAug 23, 2017
  3. Lars SchneiderAug 23, 2017
  4. Junio C HamanoAug 24, 2017
  5. Johannes SchindelinSep 15, 2017
  6. Junio C HamanoSep 15, 2017
  7. Johannes SchindelinSep 15, 2017
  8. Junio C HamanoSep 15, 2017
  9. Johannes SchindelinSep 18, 2017
  10. Junio C HamanoSep 19, 2017
  11. Johannes SchindelinSep 19, 2017
  12. Jonathan NiederSep 19, 2017
  13. Johannes SchindelinSep 29, 2017
  14. Jonathan NiederSep 19, 2017
  15. Nicolas Morey-ChaisemartinSep 19, 2017
  16. Johannes SchindelinSep 29, 2017

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.