From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32747 invoked by alias); 25 Oct 2013 16:49:46 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 32728 invoked by uid 89); 25 Oct 2013 16:49:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,TBC autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-wi0-f173.google.com Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 25 Oct 2013 16:49:45 +0000 Received: by mail-wi0-f173.google.com with SMTP id ey11so1379549wid.6 for ; Fri, 25 Oct 2013 09:49:42 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.94.167 with SMTP id dd7mr8196524wjb.43.1382719781918; Fri, 25 Oct 2013 09:49:41 -0700 (PDT) Received: by 10.194.205.136 with HTTP; Fri, 25 Oct 2013 09:49:41 -0700 (PDT) In-Reply-To: <1382719231.5918.24.camel@otta> References: <877gd5iyaz.fsf@fleche.redhat.com> <1382709091.5918.9.camel@otta> <1382719231.5918.24.camel@otta> Date: Fri, 25 Oct 2013 16:49:00 -0000 Message-ID: Subject: Re: git is live From: Fred Cooke To: Peter Bergner Cc: Tom Tromey , GDB Development , Binutils Development , Tulio Magno Quites Machado Filho Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-10/txt/msg00155.txt.bz2 That's a real shame. A possible and wasteful (resource wise) solution might be to have a second url/repo binutlils-gdb-contrib or whatever. If done locally on the same server, it could share hard links and not take up much space, but I can see the majority hating this idea, and that's fair enough. On Fri, Oct 25, 2013 at 6:40 PM, Peter Bergner wrote: > On Fri, 2013-10-25 at 16:09 +0200, Fred Cooke wrote: >> What drives the desire for that, though? With git you can publish your >> own branches as you see fit, and link them to who ever is relevant. > > I agree that from a technical standpoint, hosting a branch elsewhere > is possible with git. In my case, company policy doesn't allow it > without jumping through some painful hoops. However, I am free to > create branches in the upstream repo... as long as the project > allows it. > > > Peter > >