public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.4.25 sync unwind code with 2.6.3
Date: Thu, 04 Mar 2004 00:43:24 +0000	[thread overview]
Message-ID: <16454.31660.459217.61438@napali.hpl.hp.com> (raw)
In-Reply-To: <3792.1077504388@kao2.melbourne.sgi.com>

>>>>> On Wed, 3 Mar 2004 17:40:16 -0700, Bjorn Helgaas <bjorn.helgaas@hp.com> said:

  Bjorn> Ah, and I bet that's the one you mentioned on 2/23 with this
  Bjorn> link: http://lia64.bkbits.net:8080/to-linus-2.5/cset@1.1659
  Bjorn> (which no longer points the right place -- rats, bitten again
  Bjorn> by the fact that BK cset numbers change after the fact :-()

Argh.  Maybe we can use the stable cset numbers, but they're awfully
long.

	--david

      parent reply	other threads:[~2004-03-04  0:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  2:46 [patch] 2.4.25 sync unwind code with 2.6.3 Keith Owens
2004-02-23 20:12 ` David Mosberger
2004-03-03 23:53 ` Bjorn Helgaas
2004-03-04  0:09 ` David Mosberger
2004-03-04  0:22 ` Keith Owens
2004-03-04  0:40 ` Bjorn Helgaas
2004-03-04  0:43 ` 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=16454.31660.459217.61438@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