git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Brandon Williams <bmwill@google.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2018, #01; Thu, 2)
Date: Fri, 03 Aug 2018 14:45:28 -0700	[thread overview]
Message-ID: <xmqq600rw2dj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGZ79kZdPP+q9iuQioUU+2JkfH4n1mkkHrXaJzxGVwhxvbKZ1Q@mail.gmail.com> (Stefan Beller's message of "Fri, 3 Aug 2018 13:43:07 -0700")

Stefan Beller <sbeller@google.com> writes:

> - The second part of having an immediate plan is *very* nice
>   to see, though I would argue that it could be improved
>   by having these updates in the thread instead of summarized
>   unrelated to that thread.
>
>   We do not do this for now due to tooling issues, I suppose.

I need the current draft of "What's cooking" message that I haven't
sent out (and the committed copy on 'todo' branch, which is a copy
of what was already sent out) to be the single place I go that
drives my day-to-day integration work anyway.  I don't have time to
jump around 30-70 discussion threads (assuming there only is one
active one per each topic in flight) to see what the last tentative
verdict I gave to each one of them before deciding which ones to
merge to 'next' in day's integration run.

You are welcome to split these pieces out of the "What's cooking"
report and spray them into the original message, or write a bot to
do so.

> Is there a better way to start a workflow discussion?

My take on it is not to discuss ways to add more to other's workload
to worsen the bottleneck in the first place, and instead try to do
things you would think you can do to help, see if it actually helps,
and then after that encourage discussit as a way for others to do to
help the project, perhaps?

  reply	other threads:[~2018-08-03 21:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 23:02 What's cooking in git.git (Aug 2018, #01; Thu, 2) Junio C Hamano
2018-08-03  0:05 ` Stefan Beller
2018-08-03 16:08   ` Junio C Hamano
2018-08-03  3:00 ` Pratik Karki
2018-08-03 16:09   ` Junio C Hamano
2018-08-03 18:09 ` brian m. carlson
2018-08-03 18:40   ` Junio C Hamano
2018-08-03 18:45     ` brian m. carlson
2018-08-03 18:51       ` Junio C Hamano
2018-08-03 18:56         ` Junio C Hamano
2018-08-03 19:32           ` Brandon Williams
2018-08-03 20:07             ` Junio C Hamano
2018-08-03 20:43               ` Stefan Beller
2018-08-03 21:45                 ` Junio C Hamano [this message]
2018-08-05  6:15                 ` Junio C Hamano
2018-08-05  0:30 ` pk/rebase-in-c, was " Johannes Schindelin
2018-08-05  6:08   ` Junio C Hamano
2018-08-09 13:24     ` Johannes Schindelin
2018-08-07 10:50 ` Jakub Narebski
2018-08-07 14:36   ` Junio C Hamano
2018-08-07 15:42     ` Jakub Narębski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq600rw2dj.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=bmwill@google.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    --cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).