[mailto:openocd-
> development-boun...@lists.berlios.de] On Behalf Of David Brownell
> Sent: Saturday, October 17, 2009 3:50 PM
> To: openocd-development@lists.berlios.de
> Subject: Re: [Openocd-development] What's git's equivalent to svn
> version #?
>
> On Saturday 1
On Saturday 17 October 2009, Øyvind Harboe wrote:
> How do I figure out what version a "git describe" refers to?
git rev-parse $(git describe)
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/lis
On Wed, Oct 14, 2009 at 8:16 PM, Johannes Stezenbach wrote:
> On Wed, Oct 14, 2009 at 04:11:33PM +0200, Ųyvind Harboe wrote:
>> 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 somet
On Wed, Oct 14, 2009 at 10:11 AM, Øyvind Harboe wrote:
> 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".
They had this exact discussion on lkml last w
sion.
> -Original Message-
> From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
> development-boun...@lists.berlios.de] On Behalf Of Øyvind Harboe
> Sent: Wednesday, October 14, 2009 9:12 AM
> To: openocd-development@lists.berlios.de
> Subject: [Openocd-dev
On Wednesday 14 October 2009, Johannes Stezenbach wrote:
>
> > I was thinking about something like "0.2 + N versions".
>
> How about 'git describe'?
On one recent tree it says: "0.2.0-367-g4bc3132"
where the 367 ~= N ... good answer!
That also pretty much matches what "openocd --version" says:
On Wed, Oct 14, 2009 at 04:11:33PM +0200, Øyvind Harboe wrote:
> 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".
How about 'git describe'?
Johannes
Øyvind Harboe wrote:
> 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".
>
>
Actually you can checkout things like
$ git checkout master~2 Makefile
S
Hi!
On Wed, Oct 14, 2009 at 6:11 PM, Øyvind Harboe wrote:
> 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".
Most git-using people are happy with commi
On Wed, Oct 14, 2009 at 10:11 AM, Øyvind Harboe wrote:
> 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".
Tags are cheap in git, you can make as many a
Øyvind Harboe ha scritto:
> 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".
You can't. Just use the relevant SHA-1 id (which you can easily find by
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 progra
12 matches
Mail list logo
