From: Junio C Hamano <junkio@cox•net>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Dana How <danahow@gmail•com>,
Git Mailing List <git@vger•kernel.org>,
"Shawn O. Pearce" <spearce@spearce•org>
Subject: Re: [PATCH v3] Support ent:relative_path
Date: Sun, 06 May 2007 10:35:53 -0700 [thread overview]
Message-ID: <7v1whtdfd2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.64.0705061653100.4015@racer.site
Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
> On Sat, 5 May 2007, Junio C Hamano wrote:
>
>> Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
>>
>> >> (a) In a bare repository, I believe
>> >> setup.c:setup_git_directory_gently() determines the prefix to be
>> >> NULL. This means my patch will see ALL paths as absolute, except
>> >> :../path which will result in an error.
>> >
>> > My point was that it feels inconsistent to take the current path into
>> > account in one case, but not in the other.
>>
>> I do not understand your reasoning. In a bare repository you cannot
>> even be in a subdirectory to begin with.
>
> Exactly! That is my point. If you can do it in a working directory, but
> also with a bare repository, I find it highly confusing and inconsistent
> to have different meaning.
Sorry. Now you confused me further. I can do:
cd Documentation
git diff v1.5.0 v1.5.1 -- git.txt
Is that confusing, inconsistent and bad for the users?
next prev parent reply other threads:[~2007-05-06 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 0:47 [PATCH v3] Support ent:relative_path Dana How
2007-05-05 1:11 ` Jakub Narebski
2007-05-05 1:29 ` Johannes Schindelin
2007-05-05 3:30 ` Shawn O. Pearce
2007-05-05 19:32 ` Martin Waitz
2007-05-05 20:17 ` Junio C Hamano
2007-05-05 21:18 ` Martin Waitz
2007-05-06 0:59 ` Johannes Schindelin
2007-05-06 18:52 ` Martin Waitz
2007-05-06 23:09 ` Johannes Schindelin
2007-05-05 20:37 ` Alex Riesen
2007-05-05 3:38 ` Junio C Hamano
2007-05-05 6:46 ` Dana How
2007-05-05 8:03 ` Alex Riesen
2007-05-05 14:39 ` Johannes Schindelin
2007-05-06 6:38 ` Junio C Hamano
2007-05-06 15:14 ` Johannes Schindelin
2007-05-06 17:35 ` Junio C Hamano [this message]
2007-05-06 23:12 ` Johannes Schindelin
2007-05-07 0:18 ` Junio C Hamano
2007-05-07 0:37 ` Dana How
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=7v1whtdfd2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=danahow@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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