Martin Waitz <tali@xxxxxxxxxxxxxx> wrote:
> Do you think the approach is ok?
Looks fine from the reading part. Up to now
$ git config "$key" "$value" &&
[ "$value" = "$(git config "$key")" ] &&
echo true
will echo true for all values (at least from the things I tried with
", \ and \n). When interpreting $VAR this changes. I dunno if there
are any programs out there that rely on the fact that the value you
get out of the config is exactly the same as you have put in.
> Can you see other examples where we may need $VAR support?
> Or would everybody be happy with support for ~/ in filenames?
In my config I don't even use the path to my home directory anywhere
and spontaneously I can't think of any config option for which I'd use
an environment variable as value.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
