Commits


display the requested object type when an object could not be found ok millert@


regress: use gdate/gln if on *BSD To minimise the amount of churn between the difference in date(1) and ln(n) semantics, use gdate and gln from coreutils.


regress: fix test failures using date(1) This patch fixes test failures related the date(1) utility. In the long term we could add a wrapper function to detect valid options for date(1) and use the variant which works on the current OS. For now, this makes some tests pass and shows us where the problems are. OK thomas.adam


use the POSIX-compliant "date -u" command to return UTC time; ok stsp


add missing "return 1" to failure handling in the regress scripts ok stsp@


use POSIX [s1 = s2] syntax instead of [s1 == s2]; patch by Ryo ONODERA


switch function declarations from Korn shell to Bourne/POSIX shell syntax ok stsp


add a -q option to tests for quiet output and use it for 'make regress' Previous default output remains when test cases are run individually. ok tracey


adjust expected "object not found" error output in tests


switch 'got tag' commit argument to a -c option for consistency


fix bug in tag list tests where expected datestamps were swapped


handle Git-style "lightweight" tags in got tag -l


fix tag_list test failure on single-day-digit dates (patch by Evan Silberman)


make 'got tag -l' list tags by time stamp in descending order


create tag objects with both Git and Got during tag -l test


tweak the way 'got tag -l' displays tagged objectsI


add a colon behind object type in got tag -l, for consistency


initial implementation of 'got tag' command