git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacob Abel <jacobabel@nullpo.dev>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Linus Arver" <linusa@google.com>,
	"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: Re* [PATCH v4] MyFirstContribution: refrain from self-iterating too much
Date: Sat, 29 Jul 2023 02:12:05 +0000	[thread overview]
Message-ID: <ivxtqzb46kp5uz5luuxkow6fjzwqrnvxu6f7mgu5a4mnatt6hc@djeykymbumn6> (raw)
In-Reply-To: <xmqqa5vg59ga.fsf_-_@gitster.g>

On 23/07/28 08:42AM, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
> 
> > Jacob Abel <jacobabel@nullpo.dev> writes:
> >
> > [...]
> 
> On top of v4, we could do something like this, I guess, but I
> realize that this is talking about minimum waiting time to allow
> others to even notice-see your patches, while the original is about
> them needing time after noticing your patches to process them, and
> the latter heavily depend on many factors (like how involved the
> patches are, how many people are likely to be interested in).
> 
> So, I doubt adding this is a good idea.
>
> [...]

Maybe something along the lines of "wait 24 hours after any discussion
regarding the current revision has settled before publishing the next
revision" would be a good guideline even if it's not included in this 
patch?

But I'm realising now that that is probably outside of the scope of
this specific change so apologies for what was likely me stepping into 
the realm of bike shedding. 

I didn't mean to hold up the patch and I'm happy with v4.


  reply	other threads:[~2023-07-29  2:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  1:51 [PATCH] MyFirstContribution: refrain from self-iterating too much Junio C Hamano
2023-01-22  7:11 ` Torsten Bögershausen
2023-01-22 16:01   ` Junio C Hamano
2023-01-22 17:14     ` Junio C Hamano
2023-01-23  4:18     ` [PATCH v2] " Junio C Hamano
2023-01-23 17:58       ` Torsten Bögershausen
2023-07-19 17:04         ` [PATCH v3] " Junio C Hamano
2023-07-27 23:14           ` Linus Arver
2023-07-28  0:25             ` Junio C Hamano
2023-07-28  0:43               ` [PATCH v4] " Junio C Hamano
2023-07-28  2:07                 ` Jacob Abel
2023-07-28  5:10                   ` Junio C Hamano
2023-07-28 15:42                     ` Re* " Junio C Hamano
2023-07-29  2:12                       ` Jacob Abel [this message]
2023-07-31 15:25                         ` Junio C Hamano
2023-07-28  2:08                 ` Linus Arver
2023-07-28  5:10                   ` Junio C Hamano
2023-07-28 21:21                 ` Torsten Bögershausen
2023-07-28 23:00                   ` Junio C Hamano
2023-01-23  1:47 ` [PATCH] " Sean Allred

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=ivxtqzb46kp5uz5luuxkow6fjzwqrnvxu6f7mgu5a4mnatt6hc@djeykymbumn6 \
    --to=jacobabel@nullpo.dev \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=linusa@google.com \
    --cc=tboegi@web.de \
    /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. 
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).