Re: test files with same names?

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

 



Duy Nguyen <pclouds@xxxxxxxxx> writes:

> t2000-checkout-cache-clash.sh
> t2001-checkout-cache-clash.sh

These date back to 368f99d5 ("[PATCH 2/2] The core GIT tests: recent
additions and fixes.", 2005-05-13) which later were renamed by
f50c9f76 ("Rename some test scripts and describe the naming
convention", 2005-05-15).  One was about checking out a regular file
to a path where a directory currently sits, and the other is about
checking out a regular file that requires a parent directory at a
path where a regular file currently occupies.  These days, I suspect
that we would make these into a single "d/f conflict when checking
files out" test script, and f50c9f76 might have been a good chance
to do such a clean-up.  If somebody cares deeply enough, I do not
mind seeing a belated clean-up, either.

> t7500-commit.sh
> t7501-commit.sh
> t7502-commit.sh
> t7509-commit.sh

These seem to have organically grown and it is very likely that ones
later introduced were added more from laziness.

If somebody wants to clean them up, probably the first thing to do
is to study them to come up with a clear $test_description for each
of them.  I think t7509 says --reset-author and it may have started
as a test on that single feature, but it now covers other ways to
set and/or preserve authorship information, so it may make sense to
update its $test_description to "commit authorship" or something,
for example.




[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]

  Powered by Linux