mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@drgw.net>
To: Larry McVoy <lm@work.bitmover.com>, Tom Lord <lord@regexps.com>,
	linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: Why not an arch mirror for the kernel?
Date: Wed, 6 Mar 2002 22:56:52 -0600	[thread overview]
Message-ID: <20020306225652.Q1682@altus.drgw.net> (raw)
In-Reply-To: <200203071425.GAA06679@morrowfield.home> <20020306190419.E31751@work.bitmover.com>
In-Reply-To: <20020306190419.E31751@work.bitmover.com>; from lm@bitmover.com on Wed, Mar 06, 2002 at 07:04:19PM -0800

> > I am working on some tools that will help to implement automatic,
> > incremental, bidirectional gateways between arch, Subversion, and Bk.
> 
> Gateways, yes, bidirectional, no.  Arch doesn't begin to maintain
> the metadata which BK maintains, so it can't begin to solve the
> same problems.  If you have a bidirectional gateway, you reduce BK
> to the level of arch or subversion, in which case, why use BK at all?
> If CVS/Arch/Subversion/whatever works for you, I'd say just use it and
> leave BK out of it.

Okay Larry, reality check here... 

We really *DO* need to have more than one source control system available 
for people to use.

So maybe Arch and Subversion don't maintain all the metadata BK maintains.  
That just means that the $OTHER_SCM->BK gateway process has some manual
involvement. This is no different conceptually than sending a 'plain old
patch' in email to $MAINTAINER. 

It is in everyone's best interest to make a functional *bidirectional* 
BK<->Arch gateway. (Including you Larry)

This keeps the all the open source zealots quiet, and reduces the support 
load of Bitmover to those people that actually *want* to use Larry's stuff 
because it's better, not those that use it now because there is no '90%' 
alternative.

I'd love to see Larry and Tom sit down in a room and come up with an 
*easy* way for $MAINTAINER to take patches from both Arch and BK. (I have 
only left Subversion out because I haven't seen anyone from the project 
take an interest in making changes for kernel developers)

Now, obviously, my time would have been a lot better spent actually 
working on this myself, but I have deadlines, and wouldn't have time to 
finish it right now. So, I'm trying to spread some sanity around in the 
hopes it is contagious. (doubtfull, but I suppose I'll try)

-- 
Troy Benjegerdes | master of mispeeling | 'da hozer' |  hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's 
why I draw cartoons. It's my life." -- Charles Schulz

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 14:25 Tom Lord
2002-03-07  3:04 ` Larry McVoy
2002-03-07  4:56   ` Troy Benjegerdes [this message]
2002-03-07  5:32     ` Larry McVoy
2002-03-07 10:09       ` Jan Harkes
2002-03-07 16:15         ` Larry McVoy
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=20020306225652.Q1682@altus.drgw.net \
    --to=hozer@drgw.net \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    --cc=lord@regexps.com \
    /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

all inboxes | Powered by JetHome®