From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: yet another sparse-detected bug fix
Date: Tue, 05 Oct 2004 15:59:26 +0000 [thread overview]
Message-ID: <16738.50398.338260.501346@napali.hpl.hp.com> (raw)
In-Reply-To: <200410041545.i94FjQd0031552@napali.hpl.hp.com>
>>>>> On Tue, 5 Oct 2004 08:40:56 -0700, "Luck, Tony" <tony.luck@intel.com> said:
>> I'm confused. I posted a sparse-enablement patch yesterday. Was
>> there something wrong with that one?
Tony> I can't tell ... I haven't seen it (none of the sparse patches
Tony> that I've received match the diffstat that you sent for it
Tony> today ... and I checked the "marc.theaimsgroup.com" archive
Tony> too, it isn't there either). Please resend.
Something seems to be silently dropping mails with large patches.
Mine was just a bit over 100KB, so this seems plausible. I'm just
not sure whether it's vger or something in between.
Anyhow, I split up the patches and sent them separately anyhow since
I think they're in good enough shape that we can at least think about
merging them.
--david
prev parent reply other threads:[~2004-10-05 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 15:45 yet another sparse-detected bug fix David Mosberger
2004-10-04 19:46 ` Arun Sharma
2004-10-05 7:21 ` David Mosberger
2004-10-05 15:40 ` Luck, Tony
2004-10-05 15:59 ` David Mosberger [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=16738.50398.338260.501346@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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