From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Sixt <J.Sixt@eudaptics.com>, git@vger.kernel.org
Subject: Re: [PATCH] Support ent:relative_path
Date: Fri, 4 May 2007 21:31:42 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705042127390.4015@racer.site> (raw)
In-Reply-To: <7v1whwtmvj.fsf@assigned-by-dhcp.cox.net>
Hi,
On Fri, 4 May 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > FWIW I still find that unintuitive. I know "<something>:<path>" from ssh,
> > and there it does not change meaning depending on where I am. IMHO in most
> > cases you want to use git-diff anyway, which _does_ honour the current
> > relative path.
>
> There, its meaning is relative to where you are, namely "$HOME".
No, it is relative to where I am _at the other end_. If I "cd /tmp", it
still is relative to $HOME.
Now, what you want to do is changing the meaning of v1.5.1:Makefile,
depending if you "cd Documentation/"ed or not.
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.
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.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-04 19:31 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 [this message]
2007-05-04 19:38 ` Junio C Hamano
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=Pine.LNX.4.64.0705042127390.4015@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=J.Sixt@eudaptics.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).