public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [BK PATCH] SN update
Date: Fri, 16 May 2003 18:20:02 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705905@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705890@msgid-missing>

On Fri, May 16, 2003 at 10:49:58AM -0700, David Mosberger wrote:
> >>>>> On Fri, 16 May 2003 08:09:01 -0400, Martin Hicks <mort@wildopensource.com> said:
> 
>   Martin> On Thu, May 15, 2003 at 11:37:00PM -0700, David Mosberger
>   Martin> 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").
> 
>   Martin> I think it's "safe" to bk pull from anywhere.  There is
>   Martin> always bk unpull if you want to reverse the last pull.
> 
> That's not safe in my mind.  What I'd like is an efficient way to
> preview a pull (see a diff -u between the remote tree and where I'm
> pulling into).  Note the "efficient" part.  Having to do a full clone
> first doesn't qualify.

I found myself wishing the same thing as I tried to get together a
patch for you.  I noticed that 'bk import' has a -C option which will
let you mess with the changeset before you commit it, but 'bk receive'
doesn't, AFAIK.  It would be nice if it did (or if it was easier to
modify an existing changeset).

Jesse


  parent reply	other threads:[~2003-05-16 18:20 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
2003-05-16 16:54 ` Jesse Barnes
2003-05-16 17:49 ` David Mosberger
2003-05-16 18:20 ` Jesse Barnes [this message]
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-105590723705905@msgid-missing \
    --to=jbarnes@sgi.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