X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED4883858C2C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1629790879; bh=dnKfVWH7BYmyenhdVPH73FGjBj34gjiCfc6ibZgIQzM=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=Ef/d6XSyvIrCzw9smE2H5SSr6H2VWjZrK7aSOkN5Oo68BQ/O4ReaGxxA22SnjQxHG d9jNZzNur+U7+Qq2ipMyYPSTaIkHi/idTcRxGmN7OHm5gDugsn6RCZ5CZctMPQEr75 EFTHtp7h94/IDCvcqTWoA5WY4PT/h5mpjwtCMqXw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BFF1C3858C2C Date: Tue, 24 Aug 2021 09:40:46 +0200 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Test: cygutils 1.4.16-4 (TEST) Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <20210820203518 DOT 97ced25c9a8b228b24b6fa0f AT nifty DOT ne DOT jp> <20210822000656 DOT e12ae82f4fb91410e3a20054 AT nifty DOT ne DOT jp> <9bd9da13-ced2-343c-fed9-753975abc23b AT t-online DOT de> <7070bfc9-07c8-06da-43af-9b9c1d99032b AT maxrnd DOT com> <1b42f998-7e58-e4fa-b4f9-8732c515a0bf AT maxrnd DOT com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1b42f998-7e58-e4fa-b4f9-8732c515a0bf@maxrnd.com> X-Provags-ID: V03:K1:cIY6TjYAsRIpa9UQ37V53gCEnXHPJS0/CuTTUWB8heO2OUaDYKo 7YDGvJbVBjEPOTQdiO8IjJubHNM1UxtGFbpzOJ8VrORgWAk1akqSQJRuY+UvLr83/8VxcQH isc7j12c/NmgAGaP4uOHQOOEwm+8atC6Jk9zXBmarLfEA2OttIctlrMLDyHCuuojN/x/1I6 GHrEiIY8k5sR5kWvnaELw== X-UI-Out-Filterresults: notjunk:1;V03:K0:0oCsTSCGlcA=:KfB774yAJyQX5dKpX51a0F SUK7tRThMOhj/cm/ZnqHarvAxDIqTb8LyPj+pyNvNPMch4wraVZn3TMEQUR+zturGZ5jJlqEr AKpGTI+JiAKuQ/BWswgUcwg4huY7gkcaMqg420Kmd/0VIjnfjXQq2gGMP1XSBrOMscIvBtkqp kohEBAftqNl7gLTizh06eXzHDbCPyFrftPjxMHzJpGTbTH5tWgO0HiDPnGlvEstbPFihZfO5y 4iMbTXtHnVaFT1OAfr22mlqDEt9Ix/969Wo2EbpNngVrgOS0dxo8NCAdk/kJbI8Y/6PbjhZ86 qTt4A+eSYNwYW8ZLh9jmLqTCsCApda/+R/QwDDh5MXcEVSRJFLoMXgqb7MZJajJBntmxs4ppx sFNYMq9rw8S5bV7cW4LGeMcU+LSJInH5EzRP40A0gQVdMtLin2qN5NeklU6mdUGohlVtkPJec 0p3agzyKT2zuKNET0iVZfp4dn3l6zrFJk0/X1wzx3Dpaw5sIGXlzji3sQRHHdRb8o0WJOssgd 23eye9GfB/d0KVVsLqlVmJv7/pPOrpuQRnxyD3dW42N16rZAAIpU+1V6HIIW4L5JKp/Z4q6rD RUavsdW766XUw45tsgszZCX6hNuX97sW0CqBjFEzQb2Hxk5m3V1OlrE2tI7EmmjGBviER1L8N 9eVpzQK/B55Wd6oDt3+NlE8bpmSiI9leiYd7lKCFTgkpitwfNLqbvvvH4433tOdM6CExWkdQ4 j5/bj5e0RhmNnuTt9xXfN4TLUh88rgJRUon71HlufYRI5YMayMyA5rXJoK8jvb/xteH9Enwx4 UNxvdFfAm2WCrNf5cuuJ71+JRndyUjVGr5hHV2rFpfT+HOaiprEa2evfCrZFB3kSeYvcPdcfv 0zx7j6jb8j6WUhtlY5Gw== X-Spam-Status: No, score=-99.8 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, JMQ_SPF_NEUTRAL, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Aug 23 23:52, Mark Geisert wrote: > Mark Geisert clarifies what he wrote: > > I was also mightily confused by Charles' apparent use of git *and* a > > huge patch file. > > That's not fair. Charles used cvs; his cygutils repository was converted to > git and I've been maintaining it since the conversion. My confusion is in > whether updates are totally described by git commits or whether they > also/instead appear in the huge patch file. This is an internal issue that > I need to resolve. Ideally the public repo follows the development closely, including bugs and mistakes. We all learn only from those :) IMHO it could be pretty helpful to feed the changes from the patch file in small chunks into the repo, and then your follow up patches and reversions afterwards. So a history stays visible, even if partially faked. In case of cygutils, given how this is a Cygwin-only tool and we have full control over it, the public repo should be the one-stop-shop for code. There's no reason for a non-git patch file at all these days. > I apologize that problematic cygutils builds have been released due to my > not fully understanding the subtleties of Charles' build factory. No reason to apologize! You wrote in your mail how Chuck had his stuff in CVS originally. Additionally the stuff wasn't packed with cygport at one point. All this had a big influence on how the files were packed. I, for one, am grateful that you pull the package into modern times. > There's an upcoming cygutils-1.4.16-5 that's intended to be a clean update > that fixes the reported problems in -3 and -4test. Once that is out, the > public repository for cygutils will be updated in short order. > Thanks, Thanks to you, Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple