git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: GIT on MinGW - No symbolic links support
Date: Tue, 29 May 2007 09:11:01 +0200	[thread overview]
Message-ID: <465BD205.5D7BDF5D@eudaptics.com> (raw)
In-Reply-To: Pine.LNX.4.64.0705280054140.4648@racer.site

Johannes Schindelin wrote:
> 
> Hi,
> 
> On Sun, 27 May 2007, Aaron Gray wrote:
> 
> > Bit of a dampener on GIT on MinGW :-
> >
> >        $ git clone git://git.kernel.org/pub/scm/git/git.git
> >        Initialized empty Git repository in C:/MSYS/src/git/.git/
> >        error: git-checkout-index: unable to create symlink RelNotes (Function
> > not implemented)
> >
> > No Symbolic links !
> >
> > There are symbolic links provided by Windows by SFU (Services For Unix)
> > apparently.
> 
> Does not work on FAT. Has lots of problems.
> 
> That's why Johannes Sixt pushed for core.symlinks, and got it. So maybe
> the templates should set core.symlinks=false?

This setting should be placed into $(sysconfigdir)/gitconfig. I'll hack
up something in the next days. The "challenge" is that $(sysconfigdir)
must not be hardcoded (because the installation location is not known
until runtime). A similar thing I have already done with
$(template_dir).

-- Hannes

  reply	other threads:[~2007-05-29  7:22 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  1:13 GIT on MinGW problem Aaron Gray
2007-05-12  1:17 ` Junio C Hamano
2007-05-12  2:25   ` Aaron Gray
2007-05-12  3:30 ` Han-Wen Nienhuys
2007-05-25  8:49   ` Johannes Sixt
2007-05-25  9:45     ` Marco Costalba
2007-05-25 10:20     ` Johannes Schindelin
2007-05-25 11:07       ` Johannes Sixt
2007-05-26 19:42       ` Han-Wen Nienhuys
2007-05-26 22:17         ` Johannes Schindelin
2007-05-27  6:56           ` Han-Wen Nienhuys
2007-05-27 10:52             ` Johannes Schindelin
2007-05-27 17:04               ` Han-Wen Nienhuys
2007-05-28 16:54                 ` Nix
2007-05-27 20:44           ` Han-Wen Nienhuys
     [not found]             ` <Pine.LNX.4.64.0705272213350.4648@racer.site>
     [not found]               ` <f329bf540705271417k1874c1f2u3acc98dc25e058b9@mail.gmail.com>
2007-05-27 21:26                 ` Johannes Schindelin
2007-05-25 21:37     ` Aaron Gray
2007-05-26 19:41     ` Han-Wen Nienhuys
2007-05-26 22:26       ` Johannes Schindelin
2007-05-26 22:39         ` Junio C Hamano
2007-05-26 22:45           ` Johannes Schindelin
2007-05-26 22:53         ` Han-Wen Nienhuys
2007-05-26 23:47           ` Jakub Narebski
2007-05-27  6:30             ` Han-Wen Nienhuys
2007-05-27  6:39               ` Shawn O. Pearce
2007-05-27  7:02                 ` Han-Wen Nienhuys
2007-05-27  7:21                   ` Steven Grimm
2007-05-27  9:09                     ` Jakub Narebski
2007-05-27 23:18                       ` Han-Wen Nienhuys
2007-05-28  0:04                         ` Johannes Schindelin
2007-05-28  0:31                           ` Han-Wen Nienhuys
2007-05-27 10:46               ` Johannes Schindelin
2007-05-27 18:50       ` Han-Wen Nienhuys
2007-05-27 19:52         ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-27 20:39           ` Aaron Gray
2007-05-27 21:19             ` Han-Wen Nienhuys
2007-05-27 21:24               ` Aaron Gray
2007-05-27 21:39                 ` Aaron Gray
2007-05-27 21:55                   ` Han-Wen Nienhuys
2007-05-27 22:22                     ` Aaron Gray
2007-05-27 22:28                       ` Han-Wen Nienhuys
2007-05-27 22:56                         ` GIT on MinGW - No symbolic links support Aaron Gray
2007-05-27 23:56                           ` Johannes Schindelin
2007-05-29  7:11                             ` Johannes Sixt [this message]
2007-05-27 22:22                   ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-29 10:54       ` GIT on MinGW problem Johannes Sixt
2007-05-29 11:45         ` Marius Storm-Olsen
2007-05-29 12:10           ` Johannes Sixt
2007-05-29 14:29             ` Han-Wen Nienhuys
2007-05-29 14:49               ` Johannes Sixt
2007-05-29 12:11           ` Johannes Schindelin
2007-05-29 13:05             ` Marius Storm-Olsen
2007-05-29 13:24               ` Johannes Sixt
2007-05-29 14:36                 ` Marius Storm-Olsen
2007-05-29 13:47               ` Johannes Schindelin
2007-05-29 14:13                 ` Johannes Sixt
2007-05-29 15:28                   ` Nguyen Thai Ngoc Duy
2007-05-29 15:47                     ` Johannes Sixt
2007-05-29 18:45                       ` Nguyen Thai Ngoc Duy
2007-05-30  3:03                         ` [PATCH] Make git-k an alias to gitk Johannes Schindelin
2007-05-30  7:06                           ` Johannes Sixt
2007-05-30  2:16                       ` GIT on MinGW problem Han-Wen Nienhuys
2007-05-30  2:39                         ` Johannes Schindelin
2007-05-30  2:57                           ` Shawn O. Pearce
2007-05-30  3:25                             ` [PATCH] Git wrapper: add --redirect-stderr option Johannes Schindelin
2007-05-30  3:38                               ` Shawn O. Pearce
2007-05-30  3:45                                 ` Johannes Schindelin
2007-05-30  3:53                                   ` Shawn O. Pearce
2007-05-30  4:12                                     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465BD205.5D7BDF5D@eudaptics.com \
    --to=j.sixt@eudaptics.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).