From mboxrd@z Thu Jan 1 00:00:00 1970 From: greened@obbligato.org (David A. Greene) Subject: Re: git-subtree Ready #2 Date: Mon, 20 Feb 2012 13:34:57 -0600 Message-ID: <87pqd9wb6m.fsf@smith.obbligato.org> References: <877gztmfwy.fsf@smith.obbligato.org> <8739acra5j.fsf@smith.obbligato.org> <20120215050855.GB29902@sigill.intra.peff.net> <87sjicpsr1.fsf@smith.obbligato.org> <87ty2ro1zf.fsf@smith.obbligato.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org, Avery Pennarun To: Jeff King X-From: git-owner@vger.kernel.org Mon Feb 20 20:37:39 2012 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RzZ3G-0007kU-51 for gcvg-git-2@plane.gmane.org; Mon, 20 Feb 2012 20:37:34 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751954Ab2BTThY (ORCPT ); Mon, 20 Feb 2012 14:37:24 -0500 Received: from li209-253.members.linode.com ([173.255.199.253]:49896 "EHLO johnson.obbligato.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751653Ab2BTThX (ORCPT ); Mon, 20 Feb 2012 14:37:23 -0500 Received: from c-75-73-20-8.hsd1.mn.comcast.net ([75.73.20.8] helo=smith.obbligato.org) by johnson.obbligato.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.77) (envelope-from ) id 1RzZ3S-0006Tf-Gq; Mon, 20 Feb 2012 13:37:46 -0600 In-Reply-To: <87ty2ro1zf.fsf@smith.obbligato.org> (David A. Greene's message of "Wed, 15 Feb 2012 22:07:16 -0600") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) X-Filter-Spam-Score: () X-Filter-Spam-Report: Spam detection software, running on the system "johnson.obbligato.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: greened@obbligato.org (David A. Greene) writes: > greened@obbligato.org (David A. Greene) writes: > >>> But more important than the physical layout is the maintenance plan >>> going forward. Is Avery going to keep maintaining git-subtree, and we >>> will just occasionally pull? Are you maintaining it? Where will patches >>> go? To a github repo? To git@vger? > > I've attached Avery's response below. The short summary is that he > thinks maintaining it in the vger git repository is the way to go and > that he's fine movi Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: greened@obbligato.org (David A. Greene) writes: > greened@obbligato.org (David A. Greene) writes: > >>> But more important than the physical layout is the maintenance plan >>> going forward. Is Avery going to keep maintaining git-subtree, and we >>> will just occasionally pull? Are you maintaining it? Where will patches >>> go? To a github repo? To git@vger? > > I've attached Avery's response below. The short summary is that he > thinks maintaining it in the vger git repository is the way to go and > that he's fine moving patches to/from GitHub as necessary. So what's the next step? I guess one of the git maintaners will have to do a pull and merge. Anything I need to do on this end for that to happen? Thanks! -Dave