From: Martin Hicks <mort@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [BK PATCH] SN update
Date: Fri, 16 May 2003 12:09:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705898@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705890@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On Thu, May 15, 2003 at 11:37:00PM -0700, David Mosberger wrote:
> [Forgot to cc the list.]
>
> Jesse> Ok, this is my first 'bksend' cset, so please let me know if
> Jesse> you need something different.
>
> Please don't do that. Either send regular patches or point me to a
> tree I can pull from (actually, I still need to learn how to do this
> "safely").
I think it's "safe" to bk pull from anywhere. There is always bk unpull
if you want to reverse the last pull.
mh
--
Wild Open Source Inc. mort@wildopensource.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-16 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 6:37 [Linux-ia64] Re: [BK PATCH] SN update David Mosberger
2003-05-16 12:09 ` Martin Hicks [this message]
2003-05-16 16:54 ` Jesse Barnes
2003-05-16 17:49 ` David Mosberger
2003-05-16 18:20 ` Jesse Barnes
2003-05-16 18:41 ` David Mosberger
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-105590723705898@msgid-missing \
--to=mort@wildopensource.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