From: Bryant Bernstein <bryant.bernstein@gmail.com>
To: git@vger.kernel.org
Subject: possible problem / bug
Date: Thu, 5 May 2016 12:19:10 +1000 [thread overview]
Message-ID: <CAPpP+uW=ReKkUnz4PMEyhchcafd0qtgSZ_Qg0Hq77k4u+aPUyQ@mail.gmail.com> (raw)
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?
Bryant Bernstein
+ 61 419 323 378
next reply other threads:[~2016-05-05 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 2:19 Bryant Bernstein [this message]
2016-05-13 11:39 ` possible problem / bug 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='CAPpP+uW=ReKkUnz4PMEyhchcafd0qtgSZ_Qg0Hq77k4u+aPUyQ@mail.gmail.com' \
--to=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).