Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] sup-mail crash
Date: Tue, 10 Feb 2009 12:28:08 +0000	[thread overview]
Message-ID: <1234268739-sup-5896@tomsk> (raw)
In-Reply-To: <1234220954-sup-3688@entry>

On 9.2.2009, William Morgan wrote:
> In particular I'm pretty sure this is fixed in git, which I'll be
> releasing "any day now".

I've not been able to track sup git on my work machine for a while
because something introduced between 0.6 and latest head has borked
the mbox code. I get an odd hash error about the hash changing whilst
being read or something. Not sure how to track down what causes it
though.

I can probably update and get stack trace if its any use.

Marcus


  reply	other threads:[~2009-02-10 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 22:26 Simon Raven
2009-02-09 22:41 ` Tomas Pospisek Mailing Lists
2009-02-09 23:09   ` William Morgan
2009-02-10 12:28     ` Marcus Williams [this message]
2009-02-12 21:58       ` William Morgan
2009-02-12 22:21         ` [sup-talk] [PATCH] " Rick Tessner
2009-03-22 17:46           ` William Morgan
2009-03-23  0:04             ` Decklin Foster
2009-02-11 23:05     ` [sup-talk] " Tomas Pospisek Mailing Lists

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=1234268739-sup-5896@tomsk \
    --to=marcus-sup@bar-coded.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