From: Junio C Hamano <gitster@pobox.com>
To: Sascha Cunz <Sascha@babbelbox.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Use work tree to determine if it supports symlinks
Date: Fri, 27 Jul 2012 15:58:49 -0700 [thread overview]
Message-ID: <7vsjccyfo6.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <3068717.2K7be5iONg@mephista> (Sascha Cunz's message of "Sat, 28 Jul 2012 00:40:37 +0200")
Sascha Cunz <Sascha@babbelbox.org> writes:
> Ok, so repository and working directory are simply not meant to be on
> different file systems. Thanks for the clarification.
I did not mean "and that is a rule we need to enforce and keep
forever". I was just answering your (implied) question "why does
code comment, behaviour and documentation disagree?", to give a data
point that would be useful when discussing what the ideal behaviour
should be.
next prev parent reply other threads:[~2012-07-27 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 21:39 [RFC/PATCH] Use work tree to determine if it supports symlinks Sascha Cunz
2012-07-27 21:55 ` Junio C Hamano
2012-07-27 22:40 ` Sascha Cunz
2012-07-27 22:58 ` Junio C Hamano [this message]
2012-07-27 23:51 ` Sascha Cunz
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=7vsjccyfo6.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Sascha@babbelbox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.