public inbox for hail-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: tabled version 0.5.2 released
Date: Fri, 22 Oct 2010 23:41:03 -0400	[thread overview]
Message-ID: <4CC2594F.2070001@garzik.org> (raw)
In-Reply-To: <4CC25907.4070107@garzik.org>

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

On 10/22/2010 11:39 PM, Jeff Garzik wrote:
> Home: https://hail.wiki.kernel.org/
> Git: git://git.kernel.org/pub/scm/daemon/distsrv/tabled.git
> Download: http://www.kernel.org/pub/software/network/distsrv/tabled/
>
> Version 0.5.2 release notes (NEWS):
>
> - Permit randomly allocated TCP port, for db4 replication master
> - Install etc.tabled.conf as a useful example configuration
> - minor testsuite additions
> - many minor bug fixes
>
> Git shortlog attached.

er, now it's attached.


[-- Attachment #2: shortlog.txt --]
[-- Type: text/plain, Size: 794 bytes --]

Jeff Garzik (2):
      test/.gitignore: ignore list-keys test
      Release version 0.5.2.

Jim Meyering (6):
      server/server.c (net_write_port): Don't ignore write error.
      server/server.c: use sizeof(s) rather than equivalent "64"
      don't dereference NULL on OOM
      server/status.c: don't deref NULL on failed strdup
      server/bucket.c: don't deref NULL upon failed malloc
      adapt to changed signature of hstor_get's callback function

Pete Zaitcev (8):
      Fix crash when stopping slave
      Clean name vs host
      cleanup a call to closelog()
      Support "auto" replicaton port
      test/start-daemon: Factor 3 pid-checking if blocks into a loop.
      test/start-daemon: Ignore stale .pid files.
      Add a test for hstor_keys
      Install etc.tabled.conf


      reply	other threads:[~2010-10-23  3:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23  3:39 tabled version 0.5.2 released Jeff Garzik
2010-10-23  3:41 ` Jeff Garzik [this message]

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=4CC2594F.2070001@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.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