[Bf-translations-dev] new build versioning system is hard to follow

[Daniel Tavares]

I've been using for a few years now and I see how you'd be struggling with
the idea of follow the progression of the code base since there's no
counter to keep track of the revisions.

One thing that helps a lot to get used to this new paradigm is to make an
effort to no longer try to think of file revisions and this version
increments at each commit.

If you're on a Mac, one thing that in my opinion helps a lot for you to
understand the history of a repository is to use Gitx(1). I mainly use it
to visualize the history and inspect the branches. Aside from that, I
mostly interact with git through the terminaj.

[1] - http://rowanj.github.io/gitx/


Daniel


On Tue, Dec 3, 2013 at 3:16 PM, Bastien Montagne <montagne29 at wanadoo.fr>wrote:

>  Yeah, that’s one of the few downsides to modern distributed VCS, there is
> no more a "linear" version count really, each commit is simply identified
> by its sha hash, which just looks like a random number…
>
>
> On 04/12/2013 00:10, Daniel Tavares wrote:
>
> What is it that you don't understand?
>
> Daniel
>
>
> On Tue, Dec 3, 2013 at 2:25 PM, Gabriel Gazzán <gabcorreo at gmail.com>wrote:
>
>>  Hi all,
>>
>> Is it just my lack of enlightenment or the new build versioning system is
>> impossible to follow?
>> :-/
>>
>>  g
>>
>>
>> _______________________________________________
>> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant
>> language po file under /branches!
>>
>> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>>
>> Have some disambiguation issue (i.e. same english word that should be
>> translated in more than one way, depending on the context)? Edit this doc:
>> http://goo.gl/VzppJ
>> _______________________________________________
>> Bf-translations-dev mailing list
>> Bf-translations-dev at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>>
>>
>
>
> _______________________________________________
> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant language po file under /branches!
>
> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>
> Have some disambiguation issue (i.e. same english word that should be translated in more than one way, depending on the context)? Edit this doc: http://goo.gl/VzppJ
> _______________________________________________
> Bf-translations-dev mailing listBf-translations-dev at blender.orghttp://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>
>
> _______________________________________________
> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant
> language po file under /branches!
>
> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>
> Have some disambiguation issue (i.e. same english word that should be
> translated in more than one way, depending on the context)? Edit this doc:
> http://goo.gl/VzppJ
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-translations-dev/attachments/20131203/d5bd8dc6/attachment.htm