From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Obscure error/warning/information message from git pull Date: Fri, 14 Nov 2014 19:23:04 +0200 Message-ID: <83tx21hf2f.fsf@gnu.org> References: <20141114120604.GA3859@acm.acm> <87a93topxv.fsf@igel.home> <83h9y1j18p.fsf@gnu.org> <87r3x590k0.fsf@maru2.md5i.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1415985827 11503 80.91.229.3 (14 Nov 2014 17:23:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Nov 2014 17:23:47 +0000 (UTC) Cc: acm@muc.de, schwab@linux-m68k.org, emacs-devel@gnu.org To: Michael Welsh Duggan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 14 18:23:40 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XpKax-0003jW-Vp for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 18:23:40 +0100 Original-Received: from localhost ([::1]:37385 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpKax-00037B-IZ for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 12:23:39 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53368) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpKag-00035p-Ja for emacs-devel@gnu.org; Fri, 14 Nov 2014 12:23:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XpKac-0002IA-0t for emacs-devel@gnu.org; Fri, 14 Nov 2014 12:23:22 -0500 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:47947) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpKab-0002Hx-Ov for emacs-devel@gnu.org; Fri, 14 Nov 2014 12:23:17 -0500 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NF100A00HEFIW00@mtaout25.012.net.il> for emacs-devel@gnu.org; Fri, 14 Nov 2014 19:18:53 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NF10023VHFGC970@mtaout25.012.net.il>; Fri, 14 Nov 2014 19:18:53 +0200 (IST) In-reply-to: <87r3x590k0.fsf@maru2.md5i.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177097 Archived-At: > From: Michael Welsh Duggan > Cc: Andreas Schwab , acm@muc.de, emacs-devel@gnu.org > Date: Fri, 14 Nov 2014 12:03:43 -0500 > > Eli Zaretskii writes: > > >> From: Andreas Schwab > >> Date: Fri, 14 Nov 2014 14:46:20 +0100 > >> Cc: emacs-devel@gnu.org > >> > >> I'd be much easier if you used git new-workdir. > > > > Which Git versions are safe to use with this? What are the caveats? > > (I presume there are caveats, since you said on several occasions that > > "it is being worked on".) > > Looking at the shell script, what it does is create the new work > directory and a .git dir within it, and then symbolically links all > important files/directories from the original repository's .git > directory into the new .git dir, using ln -s. The HEAD link is copied > rather than symlinked. Yes, I've read the script (before asking ;-). > So, from Windows this will probably work if "ln -s" does something > reasonable and all the underlying stuff your version of git uses deals > with symlinks properly. (This wasn't always a reasonable assumption > under Windows in the past. You would know better than me what the > current state of symlinks on Windows is.) I wasn't asking about Windows. It is clear to me by reading the script that using that on Windows is a bad idea, because symlinks are (a) only supported since Vista, and (b) require to run the script "As Administrator". (And then there's a known caveat of removing the symlinked directory that actually removes the target, if you aren't careful to use rmdir.) No, I was asking in general about potential problems, since Andreas said several times that the feature is being improved.