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: Thu, 11 Oct 2007 21:38:12 +0100 [thread overview]
Message-ID: <b0943d9e0710111338u109aa304o6ba9c886a42c2e24@mail.gmail.com> (raw)
In-Reply-To: <20071010082602.GF12970@diana.vm.bytemark.co.uk>
On 10/10/2007, Karl Hasselström <kha@treskal.com> wrote:
> On 2007-10-09 23:46:13 +0200, Yann Dirson wrote:
> > The best situation would be that there would be a code freeze at
> > some time, during which I could update those patches without too
> > much perturbations, but that may be asking a lot :)
>
> There aren't that many of us working on StGit. If you can give a
> reasonably accurate start date and duration of the freeze,
This would mean that I have to be more organised :-).
> I don't
> think it would be a problem.Others would simply have to be aware that
> any patches not merged before the freeze would have to be rebased on
> top of your work once the freeze is over.
I'll try - let's say we freeze it starting with the coming Monday
(what's currently in kha/safe will be merged anyway) and aim to
release 0.14 in about 3 weeks (or as soon as we fix the major bugs).
--
Catalin
next prev parent reply other threads:[~2007-10-11 20:38 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
2007-10-09 21:46 ` Yann Dirson
2007-10-10 8:26 ` Karl Hasselström
2007-10-11 20:38 ` Catalin Marinas [this message]
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=b0943d9e0710111338u109aa304o6ba9c886a42c2e24@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).