All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Why not an arch mirror for the kernel?
Date: Thu, 7 Mar 2002 08:15:56 -0800	[thread overview]
Message-ID: <20020307081556.E26028@work.bitmover.com> (raw)
In-Reply-To: <200203071425.GAA06679@morrowfield.home> <20020306190419.E31751@work.bitmover.com> <20020306225652.Q1682@altus.drgw.net> <20020306213238.D3240@work.bitmover.com> <20020307100915.GA1158@mentor.odyssey.cs.cmu.edu>
In-Reply-To: <20020307100915.GA1158@mentor.odyssey.cs.cmu.edu>; from jaharkes@cs.cmu.edu on Thu, Mar 07, 2002 at 05:09:15AM -0500

On Thu, Mar 07, 2002 at 05:09:15AM -0500, Jan Harkes wrote:
> Additional metadata can be stored as comments. i.e. given the right
> tools anything that goes from a BK patchset into $SCM can be turned back
> into a BK patchset later on. Same holds for the other direction as long
> as the comments are preserved.

That's where we disagree.  I would encourage you to try it and learn for
yourself that diff&patch != BK.  I can say that it won't work and you
simply won't believe me.  Please, go try it, you'll see what I mean.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-03-07 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 14:25 Why not an arch mirror for the kernel? Tom Lord
2002-03-07  3:04 ` Larry McVoy
2002-03-07  4:56   ` Troy Benjegerdes
2002-03-07  5:32     ` Larry McVoy
2002-03-07 10:09       ` Jan Harkes
2002-03-07 16:15         ` Larry McVoy [this message]
2002-03-07 16:02       ` Troy Benjegerdes
2002-03-07 17:12       ` Henning P. Schmiedehausen
2002-03-07 21:47       ` Tom Lord
2002-03-07 16:00         ` Larry McVoy

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=20020307081556.E26028@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.