From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Lehmann Subject: Re: Composing git repositories Date: Fri, 05 Apr 2013 09:15:44 +0200 Message-ID: <515E7A20.1050003@web.de> References: <7vmwtqt8rs.fsf@alter.siamese.dyndns.org> <7vvc8comj5.fsf@alter.siamese.dyndns.org> <51537A7B.7050206@web.de> <5154AACC.7050006@web.de> <20130331225747.GB11704@elie.Belkin> <7v7gkkern9.fsf@alter.siamese.dyndns.org> <7v7gkilry2.fsf@alter.siamese.dyndns.org> <7vwqshefyk.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Junio C Hamano , Jonathan Nieder , Ramkumar Ramachandra , Git List To: Duy Nguyen X-From: git-owner@vger.kernel.org Fri Apr 05 09:16:24 2013 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 1UO0sm-00009V-SS for gcvg-git-2@plane.gmane.org; Fri, 05 Apr 2013 09:16:21 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161604Ab3DEHPw (ORCPT ); Fri, 5 Apr 2013 03:15:52 -0400 Received: from mout.web.de ([212.227.17.11]:49828 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161570Ab3DEHPv (ORCPT ); Fri, 5 Apr 2013 03:15:51 -0400 Received: from [192.168.178.41] ([79.193.90.93]) by smtp.web.de (mrweb001) with ESMTPA (Nemesis) id 0M8QaI-1UaiEz04FW-00w075; Fri, 05 Apr 2013 09:15:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 In-Reply-To: X-Enigmail-Version: 1.5.1 X-Provags-ID: V02:K0:qtRrT7NHWjtl4fBCPO3t/SUrUItUFiUIYDTphOfG0WZ MmNW8vjp/RjLKGpd4QnDavtOX+Jq0+QVo57fZUIuZQM+E5Scup /wyeGddwjJSRxyXLsXqJbJclyJ5ZqUCexMmZrNHhJLXsgFBrHO yOQPejapMA0oEYoytLSAeMM7FUZIqjhAjahb9IecRKaDhmD0hB EnWkXqY+dfzwl1KPawH+Q== Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Am 05.04.2013 07:27, schrieb Duy Nguyen: > On Fri, Apr 5, 2013 at 3:53 PM, Junio C Hamano wrote: >>> A brief summary or outcome from these links in the comment would >>> be nice. >> >> A summary of what to consider in Documentation/technical/ somewhere >> may be a very welcome addition. Thanks for volunteering ;-). > > No thanks :-) I did not really follow this thread to make such > contribution. Still have some work to do with other topics. I'll do that (unless someone else steps up). I had these links in my todo list with the intent of adding them to my github page, but I agree they make more sense in Documentation/technical. Will see when I find a time slot to read through the whole threads to give them meaningful captions.