From: Ken Brown <kbrown@cornell.edu>
To: cygwin-developers@cygwin.com
Subject: Re: branching 3.3?
Date: Thu, 28 Oct 2021 08:26:30 -0400 [thread overview]
Message-ID: <90b44271-dea2-0a8e-bb58-011749614ac5@cornell.edu> (raw)
In-Reply-To: <YXqUonfS6mQnXb9p@calimero.vinschen.de>
On 10/28/2021 8:16 AM, Corinna Vinschen wrote:
> Hi guys,
>
> what do you think about branching the Cygwin master branch into master
> and a 3.3 branch? We could add bug fixes to the 3.3 series and working
> on new 3.4 stuff in master at the same time. For 3.4 I was thinking of
> getting rid of some old cruft, as time permits.
>
> Good, bad, ugly?
Seems like a good idea. How exactly would it work? Would bug fixes get applied
to both branches? Or would 3.3 just get merged to master from time to time?
Ken
next prev parent reply other threads:[~2021-10-28 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:16 Corinna Vinschen
2021-10-28 12:26 ` Ken Brown [this message]
2021-10-28 12:46 ` Corinna Vinschen
2021-10-29 1:18 ` Mark Geisert
2021-10-29 23:11 ` Ken Brown
2021-10-30 19:17 ` Corinna Vinschen
2021-10-30 19:30 ` Ken Brown
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=90b44271-dea2-0a8e-bb58-011749614ac5@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@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).