From: Martin Waitz <tali@admingilde•org>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Junio C Hamano <junkio@cox•net>,
"Shawn O. Pearce" <spearce@spearce•org>,
Dana How <danahow@gmail•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: [PATCH v3] Support ent:relative_path
Date: Sun, 6 May 2007 20:52:59 +0200 [thread overview]
Message-ID: <20070506185259.GF30511@admingilde.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705060259460.4015@racer.site>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
hoi :)
On Sun, May 06, 2007 at 02:59:55AM +0200, Johannes Schindelin wrote:
> > On Sat, May 05, 2007 at 01:17:35PM -0700, Junio C Hamano wrote:
> > > > we could also introduce "<tree-ish>/<path>" for absolute path entries.
> > >
> > > When you name the tree-ish with usual "branch name", where does
> > > the branch name end and pathname start? What happens when there
> > > is an ambiguity, and how costly to detect such an ambiguity to
> > > begin with?
> >
> > well, if you know that it starts with a tree-ish there is no
> > ambiguity [...]
>
> Wrong. For example, mw/submodules~10 _is_ a tree-ish (if you have a branch
> named "mw/submodules").
so what?
a better argument is that one can have both refs/tags/a and
refs/heads/a/b.
So just forget my suggestion...
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-06 18:53 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 [this message]
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=20070506185259.GF30511@admingilde.org \
--to=tali@admingilde$(echo .)org \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=danahow@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--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