Re: How to handle patch series conflicts
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 9, 2018, 05:51 UTC
- Message-ID
- <xmqqh8hvr7le.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <2206767.tHxkKBSiVS@thunderbird>
Stephen & Linda Smith <ischis2@cox.net> writes:
Show 11 quoted lines
> Junio - I've been working this but would like your opinion on 7500, 7501 and > now 7510. > > I note that the the commit tests have intermixed functionality. An example is > signoff tests that are in the three tests I mentioned. > > I've been tempted multiple times over the last week to just merge the tests > into a single script, but that doesn't seem right either. > > So would you prefer a single script? Would you prefer me to move tests > around?
The scripts themselves having the same name that is no more specific tha just "commit" does not bother _me_ personally too much. If I were doing it, unless you are an obsessive type that wants to see spanking cleanness everywhere, I'd limit the changes to the minimum.
If something tested in script X is tested in another script Y and it is trivial to see they are testing exactly the same thing, removing one copy from script Y would be good, and if the remaining changes in script Y becomes more focused with only such removals, that would even be better, as at that point we can rename "tY-commit.sh" to something more specific like "tY-commit-signature.sh".