From: Dmitry Potapov <dpotapov@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-filter-branch could be confused by similar names
Date: Sun, 30 Dec 2007 13:31:46 +0300 [thread overview]
Message-ID: <20071230103146.GU13968@dpotapov.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0712292334080.14355@wbgn129.biozentrum.uni-wuerzburg.de>
Hi,
On Sat, Dec 29, 2007 at 11:36:51PM +0100, Johannes Schindelin wrote:
>
> On Tue, 25 Dec 2007, Dmitry Potapov wrote:
>
> > 'git-filter-branch branch' could fail producing the error:
> > "Which ref do you want to rewrite?" if existed another branch
> > or tag, which name was 'branch-something' or 'something/branch'.
> >
> > Signed-off-by: Dmitry Potapov <dpotapov@gmail.com>
> > ---
> > git-filter-branch.sh | 2 +-
> > t/t7003-filter-branch.sh | 10 ++++++++++
> > 2 files changed, 11 insertions(+), 1 deletions(-)
> >
> > diff --git a/git-filter-branch.sh b/git-filter-branch.sh
> > index dbab1a9..b89a720 100755
> > --- a/git-filter-branch.sh
> > +++ b/git-filter-branch.sh
> > @@ -219,7 +219,7 @@ do
> > ;;
> > *)
> > ref="$(git for-each-ref --format='%(refname)' |
> > - grep /"$ref")"
> > + grep '^refs/[^/]\+/'"$ref"'$')"
>
> Hmm. I wonder if this is a proper solution. It still does not error out
> when you have a tag and a branch of the same name.
>
Are you sure? I had created a tag and a branch with the same name, and
then tried git filter-branch on it, and it did error out:
===
warning: refname 'test1' is ambiguous.
Which ref do you want to rewrite?
===
Maybe, my fix is not a perfect solution, but it works correctly in all
known to me situations, while the original code is clearly broken in
most common cases, like when you have created a tag with a name that
consists of the name of a branch plus some arbitrary suffix. When you
run git-filter-branch on that branch, you only get: "Which ref do you
want to rewrite?", which is very confusing, because you have only one
reference with the given name.
Dmitry
next prev parent reply other threads:[~2007-12-30 10:32 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071230103146.GU13968@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).