From: Junio C Hamano <junkio@cox•net>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Johannes Sixt <J.Sixt@eudaptics•com>, git@vger•kernel.org
Subject: Re: [PATCH] Support ent:relative_path
Date: Fri, 04 May 2007 12:38:01 -0700 [thread overview]
Message-ID: <7vwszos7l2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0705042127390.4015@racer.site> (Johannes Schindelin's message of "Fri, 4 May 2007 21:31:42 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
> For me, "v1.5.1:" means something similar to ssh: it is a distant
> revision. It is not a complete filesystem. I think of revisions as
> something more general than a directory, but less general than a
> filesystem. And thus, it makes perfect sense to me that "v1.5.1:Makefile"
> means the main Makefile, no matter where I am in the current repository.
I see merits in both sides' arguments.
Saying "path out of THIS version" anchors your mindset at the
top of that version, so in that sense v1.5.1:Makefile should
mean the toplevel no matter where you are. However...
> Now, I agree that often you want to compare some file in the current
> directory to the corresponding file in a certain revision. That is why
> git-diff has a different idea, and indeed, a different notation, too.
... don't you expect "git show HEAD@{yesterday}:git.txt" while
in Documentation/ subdirectory to work? I wonder if the current
alternative "git show HEAD@{yesterday}:Documentation/git.txt" a
bit unintuitive.
next prev parent reply other threads:[~2007-05-04 19:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 7:18 [PATCH] Support ent:relative_path Dana How
2007-05-04 7:22 ` Dana How
2007-05-04 8:21 ` Junio C Hamano
2007-05-04 8:45 ` Dana How
2007-05-04 8:47 ` Alex Riesen
2007-05-04 8:53 ` Dana How
2007-05-04 9:17 ` Alex Riesen
2007-05-04 9:26 ` Dana How
2007-05-04 9:46 ` Alex Riesen
2007-05-04 16:57 ` Dana How
2007-05-04 17:17 ` Alex Riesen
2007-05-04 19:00 ` Johannes Schindelin
2007-05-04 20:23 ` Alex Riesen
2007-05-04 9:19 ` Johannes Sixt
2007-05-04 17:17 ` Junio C Hamano
2007-05-04 18:23 ` Dana How
2007-05-04 19:06 ` Johannes Schindelin
2007-05-04 19:22 ` Junio C Hamano
2007-05-04 19:31 ` Johannes Schindelin
2007-05-04 19:38 ` Junio C Hamano [this message]
2007-05-04 19:42 ` Johannes Schindelin
2007-05-04 20:21 ` Alex Riesen
2007-05-04 23:36 ` Jakub Narebski
2007-05-05 0:04 ` Junio C Hamano
2007-05-05 0:52 ` Dana How
2007-05-05 1:06 ` Jakub Narebski
2007-05-05 1:15 ` Junio C Hamano
2007-05-04 8:20 ` Alex Riesen
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=7vwszos7l2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=J.Sixt@eudaptics$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.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