From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31986 invoked from network); 13 Apr 2021 18:08:48 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 13 Apr 2021 18:08:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20200801; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=ECD6GhrBBCXaqYpclw4ATYPWG4BDOqQKNcy7IjR+af4=; b=eux4MlLtz0hkOrTA2PGyfhMkeL 334SmCy2U7GbGkIF8GS17R7Dq47vRRA5MZkiIp/9+c32eCK8aQM3gaMyh/DzSt5fXYF6qYIxo0hA3 I54WovveogDyFKWV5m5ynidnOHJJk+/nL7pIh/nsC/RhdtiIV9s8yJtj4hrjC6j+haO+7L6iGncKm IKtGqGoucxalJqyAxSQMRWrptz77oulfoqoeIIAQjqEaDlA0vOcF9FJcgsB9oqni7GldiN5Leub8e AabllTUMfoflyUB4CxzUK9AqX23ibHRggA1+PdFrP4FrxRnsz059maaQ3WRDjYlWvVXys/TQeXDH0 2WQR6aqA==; Received: from authenticated user by zero.zsh.org with local id 1lWNSy-000Ct6-Ly; Tue, 13 Apr 2021 18:08:48 +0000 Received: from authenticated user by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1lWNSk-000CcN-W2; Tue, 13 Apr 2021 18:08:35 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailauth.nyi.internal (Postfix) with ESMTP id 75C4C27C0054; Tue, 13 Apr 2021 14:08:16 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 13 Apr 2021 14:08:16 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudekledguddvudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesth hqmhdthhdtjeenucfhrhhomhepnfgrfihrvghntggvpgggvghljoiiqhhuvgiiuceolhgr rhhrhihvseiishhhrdhorhhgqeenucggtffrrghtthgvrhhnpeduvdfhfedtffdutdfgge duieegieetkeekjedugfffffevhffhveelfeegffekueenucffohhmrghinhepphhrohgu uhgtihhnghhoshhsrdgtohhmnecukfhppedutddtrdduvddrudelkedrgeegnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheplhgrrhhrhihvodhm vghsmhhtphgruhhthhhpvghrshhonhgrlhhithihqdduudehudekjeejtdegqdduudelvd ejfeekhedqlhgrrhhrhihvpeepiihshhdrohhrghesfhgrshhtmhgrihhlrdgtohhm X-ME-Proxy: Received: from [192.168.1.15] (pool-100-12-198-44.nycmny.fios.verizon.net [100.12.198.44]) by mail.messagingengine.com (Postfix) with ESMTPA id 0D11424005A; Tue, 13 Apr 2021 14:08:16 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Re: Patch bumping (was Re: Feature Patch: Use completion to view parameter values) From: =?utf-8?Q?Lawrence_Vel=C3=A1zquez?= In-Reply-To: <20210413123200.GI6819@tarpaulin.shahaf.local2> Date: Tue, 13 Apr 2021 14:08:15 -0400 Cc: Marlon , zsh-workers@zsh.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20210329171120.GA6044@tarpaulin.shahaf.local2> <20210329181452.GB6044@tarpaulin.shahaf.local2> <18618-1617324651.844569@tLsN.0hLE.FeTt> <2c44b17c-407d-449e-be2e-610db313c1d7@www.fastmail.com> <20210413123200.GI6819@tarpaulin.shahaf.local2> To: Daniel Shahaf X-Mailer: Apple Mail (2.3445.104.17) X-Seq: 48541 Archived-At: X-Loop: zsh-workers@zsh.org Errors-To: zsh-workers-owner@zsh.org Precedence: list Precedence: bulk Sender: zsh-workers-request@zsh.org X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: > On Apr 13, 2021, at 8:32 AM, Daniel Shahaf = wrote: >=20 > [Marlon: Your quote attribution line is indented one more level than = is > conventional] This is how Apple's email clients quote. I couldn't tell you why. > Leaving #4 "considerably longer" would decrease temporal locality in = the > patch authors' brains, would reap less "the project noticed my lack of > response" benefits (cf. > = https://producingoss.com/en/managing-participants.html#delegation-followup= ), > and would be more likely to find the patch author busy with other = things > and unable to follow up and post a revised patch. Good point. > You don't actually say what benefits you seek to attain. Is it about, > say, bumps that are replies to previous bumps? If so, I'd propose, = say: >=20 > - A bump that is a reply to a non-bump should be sent with delay X. >=20 > - A bump that is a reply to a bump should be sent with delay Y. >=20 > - A bump that is a reply to a bump that is a reply to a bump should be > sent with delay Z and added to git (as proposed in workers/48303). >=20 > - A bump (that is a reply to a bump)=C2=B3 should not be sent. I'm not sure about varying delays, but it would be nice to have a place to stash discussions to avoid infinite reminders. >> Additionally, it would be helpful if committers remember to inform us >> when a when a patch has been accepted/rejected/applied, >=20 > This would be helpful for other other reasons too: >=20 > - It would let the patch submitter know their patch has been accepted. > (Simply committing the patch to git without replying to it might = leave > the patch submitter think they were ignored.) >=20 > - It would make it easier for other committers (and me!) > to skip PATCH threads that have already been handled. --=20 vq=