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 21:40:56 +0300 [thread overview]
Message-ID: <20071230184056.GZ13968@dpotapov.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0712301700580.14355@wbgn129.biozentrum.uni-wuerzburg.de>
On Sun, Dec 30, 2007 at 05:03:32PM +0100, Johannes Schindelin wrote:
>
> On Sun, 30 Dec 2007, Dmitry Potapov wrote:
>
> > How about this:
> >
> > + grep '^refs/\([^/]\+/\)\?'"$ref"'$')"
>
> Maybe. I wonder whether just adding a "$" (which I obviously forgot)
> would not be enough...
Adding '$' will certainly make things much better, but you will still
have the same problem if you want to filter "master", but you have
"origin/master" in your repo.
Dmitry
next prev parent reply other threads:[~2007-12-30 18:41 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 [this message]
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=20071230184056.GZ13968@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).