Files
git/builtin
Junio C Hamano 309ca68e5a Merge branch 'js/name-rev-use-oldest-ref'
"git describe --contains" often made a hard-to-justify choice of
tag to give name to a given commit, because it tried to come up
with a name with smallest number of hops from a tag, causing an old
commit whose close descendant that is recently tagged were not
described with respect to an old tag but with a newer tag.  It did
not help that its computation of "hop" count was further tweaked to
penalize being on a side branch of a merge.  The logic has been
updated to favor using the tag with the oldest tagger date, which
is a lot easier to explain to the end users: "We describe a commit
in terms of the (chronologically) oldest tag that contains the
commit."

* js/name-rev-use-oldest-ref:
  name-rev: include taggerdate in considering the best name
2016-05-03 14:08:13 -07:00
..
2016-03-10 11:13:41 -08:00
2016-04-13 14:12:34 -07:00
2016-02-26 13:37:16 -08:00
2016-04-03 10:29:26 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-02-25 11:31:02 -08:00
2016-04-03 10:29:31 -07:00
2016-04-13 14:12:36 -07:00
2016-02-10 14:20:08 -08:00
2015-10-21 15:59:34 -07:00
2016-04-25 15:17:15 -07:00
2016-02-26 13:37:16 -08:00
2016-04-29 12:59:07 -07:00
2016-04-13 14:12:34 -07:00
2016-04-29 12:59:08 -07:00
2016-02-26 13:37:25 -08:00
2016-02-26 13:37:19 -08:00
2015-10-05 13:20:08 -07:00
2015-11-20 08:02:05 -05:00
2016-02-22 13:10:21 -08:00
2016-01-28 16:10:14 -08:00
2016-04-29 12:59:09 -07:00
2015-11-20 08:02:05 -05:00