From: jim owens <jowens@hp.com>
To: Lee Trager <lt73@cs.drexel.edu>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: experimental branch rebased
Date: Mon, 09 Mar 2009 09:26:30 -0400 [thread overview]
Message-ID: <49B51906.5010901@hp.com> (raw)
In-Reply-To: <20090307045359.GA14354@tux64-01>
Lee Trager wrote:
> Sorry it took so long to reply its been a crazy week for me.
You're lucky it was only a week, I often have crazy months!
> I can't believe I made such a stupid mistake.
Back when I started in computers, I thought 16 bits would
be more than I would ever need to count the number of times
I said that exact thing to myself.
Just another stupid mistake I made... the count overflowed :)
jim
next prev parent reply other threads:[~2009-03-09 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 15:45 experimental branch rebased Chris Mason
2009-02-26 19:05 ` Lee Trager
2009-03-03 22:07 ` jim owens
2009-03-07 4:53 ` Lee Trager
2009-03-09 13:26 ` jim owens [this message]
2009-02-26 22:54 ` Steven Pratt
2009-02-27 16:25 ` Chris Mason
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=49B51906.5010901@hp.com \
--to=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
/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