On Mon, May 30, 2011 at 04:58:14PM +0200, Romain Geissler wrote:
> Indeed the test t2050-git-dir-relative.sh run :
>
> echo changed >top &&
> git --git-dir subdir/.git add top &&
> git --git-dir subdir/.git commit -m topcommit &&
> test -r "${COMMIT_FILE}"
>
> But according to the git help, it should have specified a git-dir with --git-dir=value ie
> git --git-dir=subdir/.git add top
The test is OK. Long options that have a required argument can be
expressed as either:
--long-option=value
or
--long-option value
Long options with an optional argument must use the first form, as the
second one is ambiguous (is "value" the value, or the next option?).
Your option parser needs to follow these rules to be compatible with
git. Have you considered pulling the parse-options parser from git into
libgit2? It's one of the more modularized and lib-ified bits of code in
git already.
-Peff
--
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