From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Dana How <danahow@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v3] Support ent:relative_path
Date: Sat, 5 May 2007 03:29:44 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705050324580.4015@racer.site> (raw)
In-Reply-To: <463BD40C.6080909@gmail.com>
Hi,
On Fri, 4 May 2007, Dana How wrote:
> Most commands accept relative paths, but this is
> not true of arguments in ent:path format. This
> patch makes all of the following git-show commands
> work in the git source tree (not just the first):
> % cd xdiff
> % git-show v1.5.2-rc0:xdiff/xemit.h
> % git-show v1.5.2-rc0:./xemit.h
> % git-show v1.5.2-rc0:../sha1_name.c
ACK.
> It also adds ent:?string as a synonym for ent:/string .
> This makes the following changes possible later:
> ent:/path is an absolute path and ent:path is relative.
NACK. The "?" thing is highly unintuitive, and I still do not think that
it is worth the confusion to make Git behave funny on
<tree>:<file-name>.
Think of the "todo" branch, for example. And this is not even far fetched.
In many repositories I have to have separate related, but non-branch
HEADs. For example, I track some projects with custom scripts. These
scripts do _not_ belong into that branch. However, they are related, so I
store them in the same repository.
Plus, my example of the bare-repository still has not been answered by
_anyone_ in favour of changing the current behaviour.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-05 1:30 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 [this message]
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
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=Pine.LNX.4.64.0705050324580.4015@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=danahow@gmail.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).