public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: cygutils 1.4.16-4 (TEST)
Date: Mon, 23 Aug 2021 23:52:25 -0700	[thread overview]
Message-ID: <1b42f998-7e58-e4fa-b4f9-8732c515a0bf@maxrnd.com> (raw)
In-Reply-To: <7070bfc9-07c8-06da-43af-9b9c1d99032b@maxrnd.com>

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.

I apologize that problematic cygutils builds have been released due to my not 
fully understanding the subtleties of Charles' build factory.

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,

..mark

  reply	other threads:[~2021-08-24  6:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  7:11 Mark Geisert
2021-08-20 11:35 ` Takashi Yano
2021-08-20 23:28   ` Mark Geisert
2021-08-21 15:06     ` Takashi Yano
2021-08-23 17:48       ` Christian Franke
2021-08-23 18:10         ` Corinna Vinschen
2021-08-23 20:58           ` Mark Geisert
2021-08-24  6:52             ` Mark Geisert [this message]
2021-08-24  7:40               ` Corinna Vinschen
2021-08-23 20:51         ` Mark Geisert

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=1b42f998-7e58-e4fa-b4f9-8732c515a0bf@maxrnd.com \
    --to=mark@maxrnd.com \
    --cc=cygwin@cygwin.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.
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).