Paul Tan <pyokagan@xxxxxxxxx> writes: > Makefile | 2 +- > builtin.h | 1 + > builtin/am.c | 167 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > git.c | 1 + > 4 files changed, 170 insertions(+), 1 deletion(-) > create mode 100644 builtin/am.c > > diff --git a/Makefile b/Makefile > index 323c401..57a7c8c 100644 > --- a/Makefile > +++ b/Makefile > @@ -466,7 +466,6 @@ TEST_PROGRAMS_NEED_X = > # interactive shell sessions without exporting it. > unexport CDPATH > > -SCRIPT_SH += git-am.sh If you are building this "new am" incrementally (and for something complex like "am", that's the only sensible way), perhaps it is a good idea to do the "competing implementation" trick I suggested earlier when we were discussing your "new pull" patches, to allow you to keep both versions and switch between them at runtime. That way, you can run tests, both existing ones and new ones you add, on both versions to make sure they behave the same way. -- 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