#1845: Need comparable revision information in parrot_config output
-----------------------+----------------------------------------------------
Reporter: moritz | Owner: dukeleto
Type: bug | Status: new
Priority: blocker | Milestone: 2.10
Component: configure | Version: 2.10.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-----------------------+----------------------------------------------------
Comment(by nwellnhof):
We can always check the Parrot version, so there should never be very old
branches. I also don't see how using git-describe would avoid any problems
that can happen with SVN revisions or timestamps. AFAICS the only useful
info you get from git-describe is the number of commits that you're ahead
of a tagged commit which is probably the last official Parrot release. If
you're on a random branch this number could be anything. I think that's
even more fragile than timestamps.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1845#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
