From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [RFC] Change handling of RelNotes Date: Thu, 30 Aug 2007 23:04:21 -0700 Message-ID: <7v642w44uy.fsf@gitster.siamese.dyndns.org> References: <316a20a40708301835hc4236d4tdb289b6f705ab86@mail.gmail.com> <20070831013935.GM1219@pasky.or.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stephen Cuppett , git@vger.kernel.org To: Petr Baudis X-From: git-owner@vger.kernel.org Fri Aug 31 08:05:17 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1IQzd1-0005Vp-JT for gcvg-git@gmane.org; Fri, 31 Aug 2007 08:05:11 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760962AbXHaGFA (ORCPT ); Fri, 31 Aug 2007 02:05:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763526AbXHaGEi (ORCPT ); Fri, 31 Aug 2007 02:04:38 -0400 Received: from rune.sasl.smtp.pobox.com ([208.210.124.37]:60219 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759654AbXHaGEb (ORCPT ); Fri, 31 Aug 2007 02:04:31 -0400 Received: from pobox.com (ip68-225-240-77.oc.oc.cox.net [68.225.240.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id 67D2212AA3C; Fri, 31 Aug 2007 02:04:50 -0400 (EDT) In-Reply-To: <20070831013935.GM1219@pasky.or.cz> (Petr Baudis's message of "Fri, 31 Aug 2007 03:39:35 +0200") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Petr Baudis writes: > On Fri, Aug 31, 2007 at 03:35:36AM CEST, Stephen Cuppett wrote: >> With this one abnormality the git repo on a normal flash drive doesn't >> work... at least in my case. > > Wouldn't it be better to minimalize the restriction imposed to you by > git in case you are working on a filesystem that doesn't support > symlinks? Let's say that in that case Git will keep the symlink only in > the index... (And perhaps warn.) Didn't we already add support for Cygwin/MinGW in the form of core.symlinks configuration item? I just did this: $ git clone -l -s -n git.git victim-005 $ cd victim-005 $ git config core.symlinks false $ git checkout