On Jan 24, 2008, at 6:30 AM, Kevin Ballard wrote:
On Jan 23, 2008, at 11:37 PM, Martin Langhoff wrote:
Kevin, other people have already started posting nice nuggets of test
cases. Where are *your* test cases? That would be a nice way to "have
the last word" on this ;-)
I'm planning on devoting time this weekend to learning enough about
git to be able to start hacking. I'm just too busy during the week
to be able to devote the dedicated time necessary to this stuff.
Hopefully I'll actually be able to start producing stuff this weekend.
You do not need to learn much about git to post a test case.
Only a few lines of shell code that demonstrate how git fails to
handle a specific situation is needed. To do this, knowledge
about the internals of git does not necessary help. It should be
sufficient to know how to use git.
You may start with a simple shell script and send it to the list.
Though, a real patch would be the preferred way. For this, you
should have a quick look into the t/ subdirectory. Just open any
of the tNUMBER*.sh files. It should be quite obvious how your
sequence of shell commands could be cast into a git test script.
Steffen
-
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
