Hi, Petr!
On Thu, 2005-04-21 at 01:21 +0200, Petr Baudis wrote:
> Dear diary, on Wed, Apr 20, 2005 at 09:48:30PM CEST, I got a letter
> where Pavel Roskin <[EMAIL PROTECTED]> told me that...
> > --- a/gittrack.sh
> > +++ b/gittrack.sh
> > @@ -35,7 +35,7 @@ die () {
> > mkdir -p .git/heads
> >
> > if [ "$name" ]; then
> > - grep -q $(echo -e "^$name\t" | sed 's/\./\\./g') .git/remotes || \
> > + sed -ne "/^$name\t/p" .git/remotes | grep -q . || \
> > [ -s ".git/heads/$name" ] || \
> > die "unknown branch \"$name\""
>
> This fixes the acceptance, but not the choice.
>
> What does the grep -q . exactly do? Just sets error code based on
> whether the sed output is non-empty?
Yes.
> What about [] instead?
You'll need another pair of quotes for that:
[ "$(sed -ne "/^$name\t/p" .git/remotes)" ]; echo $?
If I remember correctly from my Autoconf hacking experience, not all
shells like mixing quotes and command substitution, and even bash
treated this differently in different versions. I can do more research,
but it seems just too fragile to me.
Another thing I remember is that "case" would not need quotes. For some
historic reasons, the expression between "case" and "in" is subjected to
command substitution, but not word expansion.
So the patch becomes:
--- a/gittrack.sh
+++ b/gittrack.sh
@@ -35,9 +35,11 @@ die () {
mkdir -p .git/heads
if [ "$name" ]; then
- grep -q $(echo -e "^$name\t" | sed 's/\./\\./g') .git/remotes || \
+ case x$(sed -ne "/^$name\t/p" .git/remotes) in
+ x)
[ -s ".git/heads/$name" ] || \
- die "unknown branch \"$name\""
+ die "unknown branch \"$name\"" ;;
+ esac
echo $name >.git/tracking
Looks rather ugly for my taste, but just in case:
Signed-off-by: Pavel Roskin <[EMAIL PROTECTED]>
By the way, please check all references to .git/remotes - this bug is
not specific to gittrack.sh.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
