From: Mark Geisert <mark@maxrnd.com>
To: cygwin-patches@cygwin.com
Subject: Re: Where should relnote updates for Cygwin DLL patches be going?
Date: Tue, 11 Jul 2023 01:49:21 -0700 [thread overview]
Message-ID: <29a23afe-7b8f-bee9-a18f-ccf6e8a66991@maxrnd.com> (raw)
In-Reply-To: <ZK0Q/o0zIKHWCJtK@calimero.vinschen.de>
Hi Corinna,
Corinna Vinschen wrote:
> On Jul 11 01:05, Mark Geisert wrote:
>> AIUI for cygwin-3_4-branch they currently go to release/3.4.8.
>> For the main|master branch they currently go where?
>
> release/3.5.0
>
> An entry there is only necessary if it doesn't get picked for 3.4
> anyway.
Ah, that helps me understand.
>> I hope to get it right the first time ;-).
>
> Is the release model confusing? If so, can you explain why?
I think I haven't been paying close enough attention and have been doing the
relnote updates by rote. But there being two active branches and I
(understandably) don't determine which releases my commits go to means I should
wait until they show up on the cvs-patches list, then I will know which relnote
files to update. That should work OK, right?
Is it preferred that relnote updates should be separate patches from the code updates?
Thanks,
..mark
next prev parent reply other threads:[~2023-07-11 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:05 Mark Geisert
2023-07-11 8:21 ` Corinna Vinschen
2023-07-11 8:49 ` Mark Geisert [this message]
2023-07-11 9:45 ` Corinna Vinschen
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=29a23afe-7b8f-bee9-a18f-ccf6e8a66991@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-patches@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).