jjengla@xxxxxxxxxx writes:
> From: Josh England <jjengla@xxxxxxxxxx>
>
> This adds a post-merge hook that will run after `git pull` operations
> if enabled. The hook is passed no arguments and cannot affect the
> outcome of a merge.
>
> Signed-off-by: Josh England <jjengla@xxxxxxxxxx>
Thanks for your patch.
Two questions.
* Do you want to run the post-merge hook even for a squash
merge?
* After resolving a conflicted merge, you would conclude it
with "git commit"; don't you want to have the same hook apply
at the commit time, or is that what you expect the user to
deal with with post-commit hook?
And two requests and a half.
- We would want a new test in the test suite for this, to make
sure that later changes by others would not break this new
feature you would depend upon.
- You described _what_ the patch and the new feature do in the
log message and in the documentation.
You need to also explain _why_ somebody might want to have
such a hook in his repository.
. In the documentation, you would want to make the reader
realize "aha, this is something that would help me" with an
example.
. In the log message, you would want to make sure other
people understand why this new feature was added, what the
design consideration were at the point of the feature was
added.
The latter is important to me personally. I want to have
something better than "this change does not break anything
existing, and it is something somebody wants to get added, so
while I can not image the exact use scenario why anybody
would want to use such a hook I'd apply the change" to
convince myself.
- We are deep in feature-freeze for 1.5.3; I'd appreciate a
resend for any patch that is not a bugfix / documentation
update after 1.5.3 final.
-
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
