Re: [PATCH] Convert t6022 to use git-merge instead of git-pull

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andy Whitcroft <apw@xxxxxxxxxxxx> writes:

> Junio C Hamano wrote:
>> Is this really necessary?
>> 
>> I would rather want to leave some tests use "git merge" while
>> some others use "git pull ." to catch breakage of either form.
>
> If we are saying git pull . foo and git merge foo forms are the same
> then perhaps that whole bunch of tests should be converted such that
> they are in for cmd in "merge" "pull ." loop, so we test both always.

Not "whole bunch" needs to check they are the same.  Ideally we
would want to have a single separate test whose sole purpose is
to make sure they are the same, but if we do not have such a
test, the next best thing is to leave some test to use one way
while some others to use another.  In other words, consistency
is not necessarily better than diversity in tests.

-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]