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 15, 2017, 16:18 UTC
Message-ID
<alpine.DEB.2.21.1.1709151816390.219280@virtualbox>
In-Reply-To
<xmqq1so0wyjd.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Thu, 24 Aug 2017, Junio C Hamano wrote:
Show 37 quoted lines
> Lars Schneider <larsxschneider@gmail.com> writes:
> 
> > On 22 Aug 2017, at 21:56, Junio C Hamano <gitster@pobox.com> wrote:
> >
> >> Here are the topics that have been cooking.  Commits prefixed with
> >> '-' are only in 'pu' (proposed updates) while commits prefixed with
> >> '+' are in 'next'.  The ones marked with '.' do not appear in any of
> >> the integration branches, but I am still holding onto them.
> >> 
> >> The second batch of topics are in.  This cycle is going a bit slower
> >> than the previous one (as of mid-week #3 of this cycle, we have
> >> about 200 patches on 'master' since v2.14, compared to about 300
> >> patches in the cycle towards v2.14 at a similar point in the cycle),
> >> but hopefully we can catch up eventually.  
> >> 
> >> I am planning to be offline most of the next week, by the way.
> >> 
> >> You can find the changes described here in the integration branches
> >> of the repositories listed at
> >> 
> >>    http://git-blame.blogspot.com/p/git-public-repositories.html
> >> 
> >> --------------------------------------------------
> >> [Graduated to "master"]
> >> 
> >
> > Hi Junio,
> >
> > just in case this got lost: I posted a patch with an improvement to 
> > 2841e8f ("convert: add "status=delayed" to filter process protocol", 
> > 2017-06-30) which was merged to master in the beginning of 2.15.
> >
> > https://public-inbox.org/git/20170820154720.32259-1-larsxschneider@gmail.com/
> 
> Thanks for pinging, but next time ping the thread itself if it is
> about something that is not in What's cooking report you are
> responding to.

If you want *contributors* to ping the thread themselves, how about *posting your updates there, too*?

It does make things inconvenient for contributors if they have to monitor those Whats' cooking emails in addition to the mail threads, you know?

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 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.