From: Bjorn Helgaas <bjorn_helgaas@hp.com>(by way of Bjorn Helgaas <bjorn_helgaas@hp.c
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [patch] 2.4.20 unwind.c to handle multiple struct pt_regs
Date: Tue, 11 Mar 2003 16:23:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806023@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805882@msgid-missing>
[Sorry if this is a duplicate; I sent it yesterday, but it bounced due
to an HP mail problem.]
On Monday 03 March 2003 4:52 pm, Keith Owens wrote:
> On Mon, 3 Mar 2003 09:47:49 -0700,
> Bjorn Helgaas <bjorn_helgaas@hp.com> wrote:
> >Wow, somebody is actually looking at the BK tree :-)
>
> I do not use BK. Because I work on PRCS I am not comfortable with
> using BK, there is a possible conflict with the BK 'no competitor'
> clause. I was looking at Marcelo's 2.4.21-pre5 patch.
Yeah, that makes sense. BK is extremely convenient for me, because
it makes it so easy to track what Marcelo and David are doing, but
I certainly don't want to force that on anybody else.
It feels like the "right thing" to make plain old patches available
whenever I publish changes via BK, and I'm willing to do that if
there's any interest in it.
Bjorn
next prev parent reply other threads:[~2003-03-11 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 1:29 [Linux-ia64] Re: [patch] 2.4.20 unwind.c to handle multiple struct pt_regs Keith Owens
2003-03-02 5:15 ` Keith Owens
2003-03-03 16:47 ` Bjorn Helgaas
2003-03-03 23:52 ` Keith Owens
2003-03-04 22:06 ` David Mosberger
2003-03-07 19:22 ` Bjorn Helgaas
2003-03-11 16:23 ` Bjorn Helgaas [this message]
2003-03-12 1:54 ` Keith Owens
2003-03-12 2:58 ` Matthew Wilcox
2003-03-12 7:22 ` [Linux-ia64] Re: [patch] 2.4.20 unwind.c to handle multiple David Woodhouse
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=marc-linux-ia64-105590709806023@msgid-missing \
--to=bjorn_helgaas@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