From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup-sync dies; memory limit?
Date: Tue, 12 May 2009 12:54:35 -0700 [thread overview]
Message-ID: <1242158027-sup-1409@entry> (raw)
In-Reply-To: <20090512183158.GO28854@pimlott.net>
Reformatted excerpts from Andrew Pimlott's message of 2009-05-12:
> It doesn't seem possible that the git copy of sup affected the
> installed gem. So I'm at a complete loss too.
Let's just pretend this never happened.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-05-12 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 16:42 Andrew Pimlott
2009-05-11 18:26 ` Andrew Pimlott
2009-05-12 17:19 ` William Morgan
2009-05-12 18:31 ` Andrew Pimlott
2009-05-12 19:54 ` William Morgan [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=1242158027-sup-1409@entry \
--to=wmorgan-sup@masanjin.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