Well, that won't really work since history is nonlinear. You can "git log --oneline -- path/to/file" to list out the last commit to modify that file. Then "git describe <abbreviated_hash_from_first_line_of_log>" and it'll give you something like: tagname-<commit-count-since>-g<Abbreviated SHA1> which is a valid way to specify a revision.
> -----Original Message----- > From: [email protected] [mailto:openocd- > [email protected]] On Behalf Of Øyvind Harboe > Sent: Wednesday, October 14, 2009 9:12 AM > To: [email protected] > Subject: [Openocd-development] What's git's equivalent to svn version > #? > > What's the most reasonable way to refer to a git version > for human beings? > > In svn it's a small integer("only" in the thousands). > > I was thinking about something like "0.2 + N versions". > > -- > Øyvind Harboe > http://www.zylin.com/zy1000.html > ARM7 ARM9 ARM11 XScale Cortex > JTAG debugger and flash programmer > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
