From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dmitry Potapov <dpotapov@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-filter-branch could be confused by similar names
Date: Sat, 5 Jan 2008 16:03:55 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0801051601490.10101@racer.site> (raw)
In-Reply-To: <7vr6gxjpyn.fsf@gitster.siamese.dyndns.org>
Hi,
On Fri, 4 Jan 2008, Junio C Hamano wrote:
> Dmitry Potapov <dpotapov@gmail.com> writes:
>
> > It works only if the name "unambiguous" for git show-ref, which
> > interprets refname differently than rev-list as I wrote above.
> > Nevertheless, I believe we can use 'git show-ref' if we try something
> > like this:
>
> Ahh.
>
> But at that point I would say that exposing the refname dwimming
> logic to the scripts could be a much cleaner solution.
I considered that when ripping the script from cogito, but it seemed to me
at that time that not requiring an up-to-date git for testing the script
would be better.
Now is a different situation, however, so I agree.
Ciao,
Dscho
next prev parent reply other threads:[~2008-01-05 16:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-25 14:35 [PATCH] git-filter-branch could be confused by similar names Dmitry Potapov
2007-12-29 22:36 ` Johannes Schindelin
2007-12-30 10:31 ` Dmitry Potapov
2007-12-30 10:46 ` Johannes Schindelin
2007-12-30 13:54 ` Dmitry Potapov
2007-12-30 16:03 ` Johannes Schindelin
2007-12-30 18:40 ` Dmitry Potapov
2007-12-30 18:51 ` Dmitry Potapov
2008-01-03 21:27 ` Junio C Hamano
2008-01-04 15:51 ` Dmitry Potapov
2008-01-04 20:28 ` Junio C Hamano
2008-01-05 16:03 ` Johannes Schindelin [this message]
2008-01-05 20:23 ` [PATCH 1/2] git-rev-parse --symbolic-full-name Junio C Hamano
2008-01-05 20:28 ` [PATCH 2/2] filter-branch: work correctly with ambiguous refnames Junio C Hamano
2008-01-06 1:57 ` Johannes Schindelin
2008-01-06 2:53 ` Junio C Hamano
2008-01-06 9:14 ` Johannes Schindelin
2008-01-05 1:17 ` [PATCH] git-filter-branch could be confused by similar names Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.1.00.0801051601490.10101@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).