From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Yann Dirson" <ydirson@altern.org>,
"David Kågedal" <davidk@lysator.liu.se>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Status of kha/experimental
Date: Tue, 9 Oct 2007 22:10:12 +0100 [thread overview]
Message-ID: <b0943d9e0710091410w1559f1a0yb5055182fd289646@mail.gmail.com> (raw)
In-Reply-To: <20071007213307.GA32210@diana.vm.bytemark.co.uk>
On 07/10/2007, Karl Hasselström <kha@treskal.com> wrote:
> On 2007-10-07 22:18:44 +0100, Catalin Marinas wrote:
>
> > How stable is the kha/experimental branch? Since there are more and
> > more bugs added to the tracking system, I'll have to start looking
> > at them before a 0.14 release. Is it worth merging the
> > kha/experimental now or we better wait for after 0.14?
>
> The idea is that experimental contains changes that need testing, but
> may not yet be ready for your master. (They are generally safe,
> though; I run StGit from my experimental branch at work, for example.)
> When I decide that they are ready, I move them to safe. If there are
> any patches you feel should be in safe rather than experimental, just
> ask. Or you could just take them directly from experimental without
> asking, of course. :-)
OK. My plan is to merge kha/safe and have a look at what seems safer
to merge from kha/experimental. Fix bugs (and freeze the current
features). Release 0.14. Merge kha/experimental entirely post 0.14 and
test/stabilize it over couple of months. How does this sound?
--
Catalin
next prev parent reply other threads:[~2007-10-09 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 21:18 Status of kha/experimental Catalin Marinas
2007-10-07 21:33 ` Karl Hasselström
2007-10-09 21:10 ` Catalin Marinas [this message]
2007-10-09 21:46 ` Yann Dirson
2007-10-10 8:26 ` Karl Hasselström
2007-10-11 20:38 ` Catalin Marinas
2007-10-12 7:43 ` Karl Hasselström
2007-10-12 8:56 ` Catalin Marinas
2007-10-10 7:39 ` David Kågedal
2007-10-10 8:17 ` Karl Hasselström
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=b0943d9e0710091410w1559f1a0yb5055182fd289646@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=ydirson@altern.org \
/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 NNTP newsgroup(s).