Re: [PATCHv2] git bisect old/new

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

 



Phil Hord <phil.hord@xxxxxxxxx> writes:

> Except that most of the work to support <arbitrary1/arbitrary2> is
> already being done in this patch to add <new/old>, but it will need
> re-doing or un-doing to move to arbitrary terms.  Supporting arbitrary
> terms today would save work (the re-doing and the un-doring), if we
> went that way in the future.

You are forgetting that "somebody wrote the code" does not matter
much.  What counds more is that the code is more complex than
necessary to support the case we are immediately interested in,
which means it is much more likely to have undiscovered bugs and
will take more effort to update if we need to change the aspects
other than "arbitrary two tokens" later.  "Somebody wrote the code
already" matters only when we are sure that we want to build on top
of it. In this case, we don't.
--
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]