git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Bryant Bernstein <bryant.bernstein@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: possible problem / bug
Date: Fri, 13 May 2016 13:39:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1605131338480.4092@virtualbox> (raw)
In-Reply-To: <CAPpP+uW=ReKkUnz4PMEyhchcafd0qtgSZ_Qg0Hq77k4u+aPUyQ@mail.gmail.com>

Hi Bryant,

On Thu, 5 May 2016, Bryant Bernstein wrote:

> Both windows and linux support links but both git and the git bash
> seem to have a problem with them.
> 
> In my source, (originally on Linux) I have a link in my source
> directory to a config file which I normally import into python.  This
> allows me to have something.py pointing to config.txt .  config.txt
> can be opened by an editor and something.py can be imported into a
> python shell.
> 
> This worked in Linux alone and on windows  as both platforms support
> links.  But if I use git to bring my code from linux to windows I end
> up with a file that contains the path to the target file.
> 
> Then I went to try to see what git bash would do with a link.
> 
> I created a file and a link to it using ln -s
> This created a copy of the file I wanted to link to.
> 
> What do you think?
> Should this work better?

See https://github.com/git-for-windows/git/wiki/Symbolic-Links

Ciao,
Johannes

      reply	other threads:[~2016-05-13 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05  2:19 possible problem / bug Bryant Bernstein
2016-05-13 11:39 ` Johannes Schindelin [this message]

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=alpine.DEB.2.20.1605131338480.4092@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=bryant.bernstein@gmail.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).