From: Paul Jackson <pj@sgi•com>
To: Pavel Roskin <proski@gnu•org>
Cc: git@vger•kernel.org, pasky@ucw•cz
Subject: Re: [PATCH] gittrack.sh accepts invalid branch names
Date: Wed, 20 Apr 2005 16:22:34 -0700 [thread overview]
Message-ID: <20050420162234.3ccbf23e.pj@sgi.com> (raw)
In-Reply-To: <1114026510.15186.15.camel@dv>
Pavel wrote:
> sed -ne "/^$name\t/p" .git/remotes | grep -q .
Consider using the following to look for a match of $name with
the first tab separated field of the remotes file (and to avoid
using 'grep -q', which is not in all grep's, so far as I know):
cut -f1 .git/remotes | grep -Fx "$name" >/dev/null
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr•sgi.com> 1.650.933.1373, 1.925.600.0401
prev parent reply other threads:[~2005-04-20 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 19:48 [PATCH] gittrack.sh accepts invalid branch names Pavel Roskin
2005-04-20 23:21 ` Petr Baudis
2005-04-21 1:28 ` Pavel Roskin
2005-04-20 23:22 ` Paul Jackson [this message]
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=20050420162234.3ccbf23e.pj@sgi.com \
--to=pj@sgi$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pasky@ucw$(echo .)cz \
--cc=proski@gnu$(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