From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Patch bumping (was Re: Feature Patch: Use completion to view parameter values)
Date: Wed, 14 Apr 2021 12:52:01 +0000 [thread overview]
Message-ID: <20210414125201.GD3882@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <2EE1CCA0-E8C3-4A9F-898B-F823890EA58C@zsh.org>
Lawrence Velázquez wrote on Tue, Apr 13, 2021 at 17:31:30 -0400:
> On Apr 13, 2021, at 9:35 AM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > Regarding your taxonomy, would it be accurate to say that in cases
> > A and B a submitted patch is awaiting resolution, whereas in case C it's
> > generally a design question that's awaiting resolution? In A+B the
> > person in question is the patch submitter; in C the person in question
> > is probably a regular developer.
>
> Many type C discussions are just a committer saying "I'm thinking
> about committing this, what does everyone think?" and then waiting
> on any feedback, from nitpicks to overarching design critique.
In these, I think it matters whether the "this" referred to is the
committer's work or a patch submitter's work. In the latter case, it's
essentially case A again.
> > (Aside: Note the terminology: "developer", not "committer", since in
> > general, distinctions between people who do and don't have commit access
> > shouldn't be made, except when it's necessary to actually invoke «git
> > push».¹)
>
> Sure, but commit access is relevant to patch discussions involving
> noncommitting contributors (types A and B) because the commit step
> is often the only thing holding things up.
Personally, I don't recall that many threads ending with "the patch
LGTM, just need to push it when I'll get home" or similar.
> > No comment from me on case C.
>
> Should I continue bumping developer-only patch discussions at all?
> If so, I'm inclined to let them simmer for longer -- perhaps a month
> (as per workers/48516). I feel pretty pesky basically reminding
> committers to commit their own patches, but everyone forgets things
> now and then. Is it helpful or annoying?
Personally, I keep on my todo list patches I've posted, but not patches
I've reviewed or random ideas I've floated. I suspect that in general
reminders would be helpful when a patch submission requests
feedback/comments/reviews or asks a question.
Cheers,
Daniel
next prev parent reply other threads:[~2021-04-14 12:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 20:53 Feature Patch: Use completion to view parameter values Marlon Richert
2021-03-29 7:39 ` Daniel Shahaf
2021-03-29 11:55 ` Marlon Richert
2021-03-29 17:11 ` Daniel Shahaf
2021-03-29 17:20 ` Bart Schaefer
2021-03-29 18:14 ` Daniel Shahaf
2021-03-29 20:00 ` Marlon Richert
2021-03-29 20:05 ` Daniel Shahaf
2021-03-29 20:35 ` Marlon Richert
2021-04-01 4:28 ` Marlon Richert
2021-04-01 18:40 ` Daniel Shahaf
2021-04-02 0:50 ` Oliver Kiddle
2021-04-10 20:20 ` Lawrence Velázquez
2021-04-11 20:06 ` Marlon Richert
2021-04-11 21:24 ` Patch bumping (was Re: Feature Patch: Use completion to view parameter values) Bart Schaefer
2021-04-12 8:18 ` Marlon
2021-04-13 12:32 ` Daniel Shahaf
2021-04-13 18:08 ` Lawrence Velázquez
2021-04-15 9:39 ` [META] Tone of voice / Writing style in patch reviews (was Re: Patch bumping) Marlon
2021-04-15 10:33 ` zeurkous
2021-04-13 13:35 ` Patch bumping (was Re: Feature Patch: Use completion to view parameter values) Daniel Shahaf
2021-04-13 21:31 ` Lawrence Velázquez
2021-04-13 21:50 ` Bart Schaefer
2021-04-14 12:52 ` Daniel Shahaf [this message]
2021-04-13 2:47 ` Lawrence Velázquez
2021-04-12 20:22 ` Feature Patch: Use completion to view parameter values Marlon
2021-04-12 21:49 ` Bart Schaefer
2021-04-13 4:50 ` Marlon Richert
2021-03-30 5:41 ` Mikael Magnusson
2021-03-31 22:55 ` Daniel Shahaf
2021-03-31 23:03 ` Daniel Shahaf
2021-03-29 20:10 ` Peter Stephenson
2021-03-29 11:48 ` Mikael Magnusson
2021-03-29 12:06 ` Marlon Richert
2021-03-29 12:07 ` Marlon Richert
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=20210414125201.GD3882@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.org \
/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://git.vuxu.org/mirror/zsh/
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).