From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org, "Samuel Tardieu" <sam@rfc1149.net>,
"Daniel White" <daniel@whitehouse.id.au>
Subject: Re: [StGit] kha/{safe,experimental} updated
Date: Wed, 13 Aug 2008 22:54:57 +0100 [thread overview]
Message-ID: <b0943d9e0808131454p16cb104bs1bcf67a6c660a88a@mail.gmail.com> (raw)
In-Reply-To: <20080808082728.GA24017@diana.vm.bytemark.co.uk>
2008/8/8 Karl Hasselström <kha@treskal.com>:
> Catalin has pulled the safe and stable branches, but I've accumulated
> some new stuff in kha/safe.
I merged it, thanks.
> The stack log stuff (and nothing else) is still in kha/experimental.
> It's unchanged since my last status mail, except for the addition of
> an optimization at the end (will post as a follow-up to this mail).
I'm on holiday until Monday and I haven't got the time to test the
performance but we can probably move the experimental stuff into
master and start preparing some release candidates. I'll repost my
patches with the new git id format as well and we need a 0.14.4 in the
meantime (hopefully over the next two weeks).
Thanks.
--
Catalin
next prev parent reply other threads:[~2008-08-13 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 8:27 [StGit] kha/{safe,experimental} updated Karl Hasselström
2008-08-08 8:07 ` [StGit PATCH] Read several objects at once with git cat-file --batch Karl Hasselström
2008-08-10 22:25 ` Catalin Marinas
2008-08-10 23:58 ` Karl Hasselström
2008-08-13 21:54 ` Catalin Marinas [this message]
2008-08-17 20:18 ` [StGit] kha/{safe,experimental} updated Karl Hasselström
2008-08-21 22:16 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2008-09-21 15:37 Karl Hasselström
2008-09-24 22:48 ` Catalin Marinas
2008-09-25 7:33 ` Karl Hasselström
2008-12-08 20:39 Karl Hasselström
2008-12-10 20:40 ` 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=b0943d9e0808131454p16cb104bs1bcf67a6c660a88a@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=daniel@whitehouse.id.au \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=sam@rfc1149.net \
/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).