From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-12598-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 29122 invoked by alias); 19 Feb 2003 19:35:37 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 29106 invoked from network); 19 Feb 2003 19:35:36 -0000
Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136)
  by 172.16.49.205 with SMTP; 19 Feb 2003 19:35:36 -0000
Received: (from carlton@localhost)
	by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h1JIbx930587;
	Wed, 19 Feb 2003 10:37:59 -0800
X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [maint] The GDB maintenance process
References: <20030217180709.GA19866@nevyn.them.org>
	<20030218042847.50F2E3CE5@localhost.redhat.com>
	<20030218023553.2BBB73D02@localhost.redhat.com>
	<15953.20132.193102.752916@localhost.redhat.com>
	<20030219014904.GA11446@nevyn.them.org> <3E539ABA.4050203@redhat.com>
	<ro1y94c89at.fsf@jackfruit.Stanford.EDU>
	<1030219175720.ZM8839@localhost.localdomain>
From: David Carlton <carlton@math.stanford.edu>
Date: Wed, 19 Feb 2003 19:35:00 -0000
In-Reply-To: <1030219175720.ZM8839@localhost.localdomain>
Message-ID: <ro1u1f086bc.fsf@jackfruit.Stanford.EDU>
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2003-02/txt/msg00371.txt.bz2

On Wed, 19 Feb 2003 10:57:20 -0700, Kevin Buettner <kevinb@redhat.com> said:

> For the contract work that Red Hat itself does, Red Hat does not
> depend solely on the external (sources.redhat.com) respository.  Red
> Hat has an internal repository that it uses for customer work.  From
> time to time, the public repository is merged to Red Hat's internal
> repository.  Also, from time to time, work that was performed for a
> customer which couldn't immediately go into the public repository is
> pushed out to the public.

Thanks for the info; that sounds sensible.

It would be nice if there were a scheme that allowed such development
to go on smoothly while still making it as easy as possible for
changes in separate repositories to make it into the mainline.  I
don't really know to do that, though.

David Carlton
carlton@math.stanford.edu