On Sat, Nov 16, 2013 at 11:51 PM, GSR gsr@infernal-iceberg.com wrote:
brechtvanlom...@pandora.be (2013-11-15 at 2039.00 +0100):
Sending a reminder for after the switch to git, we have guidelines for
how to format your commit logs to keep it all easy to scan quickly,
understand for users
You may have noticed that source/tools and intern/tools aren't in
blenders git repo.
Some have been moved to:
http://git.blender.org/gitweb/gitweb.cgi/blender-dev-tools.git
- readme.rst has more details.
The main reason for this is so we can be more relaxed about adding
utilities, scripts,
In the wiki, how do we make a link to the git commit log?
IRIE Shinsuke
13/11/17, Brecht Van Lommel wrote:
Hi,
Just a friendly reminder to add new features to release notes immediately:
http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.70
I'm replying to this particular commit, but
See this page:
http://wiki.blender.org/index.php/Template:GitCommit
On Sun, Nov 17, 2013 at 10:25 AM, IRIE Shinsuke
irieshins...@yahoo.co.jp wrote:
In the wiki, how do we make a link to the git commit log?
IRIE Shinsuke
13/11/17, Brecht Van Lommel wrote:
Hi,
Just a friendly reminder to
Thanks, I couldn't find that page.
IRIE Shinsuke
13/11/17, Brecht Van Lommel wrote:
See this page:
http://wiki.blender.org/index.php/Template:GitCommit
On Sun, Nov 17, 2013 at 10:25 AM, IRIE Shinsuke
irieshins...@yahoo.co.jp wrote:
In the wiki, how do we make a link to the git commit log?
Maybe a slight switch of priorities: Use new-user-friendly names and put
the phabricator name as the explanation? Then most users will not need the
explanation and it is more a hint for experienced phabricator users...
On Sat, Nov 16, 2013 at 11:53 AM, Peter Schlaile pe...@schlaile.de wrote:
hi,
I wasn't sure exactly how to reach out for helping. I am interested in
helping out with the UI design/development team. I do a mix of design and
development at my job, so I am ok doing coding as well as creating mockups
for improvements.
I grabbed the blender source and have it compiling.
Hi all,
Here are the notes from today's meeting in irc.freenode.net #blendercoders.
1) Migration to git and Phabricator
- Blender entered a new era of software development! What started with manual
backups (1994), moved to cvs (2000), svn (2007) and now to git (2013). It's
almost the 7 year
Hey,
Just to address common questions and draw some outline of what's happening
now.
- Git repositories are considered final and open for push
- For push you need to use SSH protocol (url like
g...@git.blender.org:blender.git
url).
- You should have a RSA key which you upload in
Hi Campbell,
In the Freestyle Python API, StopIteration is used to implement the
generic Python iterator protocol. In addition, the API allows users to
increment an iterator manually through the iterator's .increment()
method. When the iteration is over N elements, manual iteration ends
Hi everyone,
I'd like to give you notice of a somewhat advanced git HOWTO for people
that used previout git mirrors of blender (as the mirror by jesterKing).
The HOWTO is here:
http://wiki.blender.org/index.php/User:Frnchfrgg/Transplant
This HOWTO aims to salvage developement branches made
Hi everyone,
I'd like to give you notice of a somewhat advanced git HOWTO for people
that used previout git mirrors of blender (as the mirror by jesterKing).
The HOWTO is here:
http://wiki.blender.org/index.php/User:Frnchfrgg/Transplant
This HOWTO aims to salvage developement branches made
Here's what I did:
* Create a copy of my git-svn repo to avoid messing it up (I will refer to
this as copy-repo).
* cd to the copied repo
* Make the blender folder the root of the repot with: git filter-branch
--subdirectory-filter blender/ -- --all
* cd into your new Blender repo
* Add your
Just a quick clarification, is just 2.70 allowed to break compatibility, or
is the 2.7x line allowed to do this similar to 2.5x development?
--Mitchell Stokes
On Sun, Nov 17, 2013 at 8:31 AM, Ton Roosendaal t...@blender.org wrote:
Hi all,
Here are the notes from today's meeting in
We appear to have lost our categories for the BGE bug tracker. We used to
have categories such as animation, rendering, physics, logic, audio, etc.
Now we just have a mess of BGE bugs. Also, is there a way to get an idea
of how many bugs there are? When I'm in Maniphest, it just tells me how
many
On Mon, Nov 18, 2013 at 1:34 AM, Mitchell Stokes moguri...@gmail.com wrote:
Another thing, do we need an OpenGL Error task type when we have an
OpenGL/Gfx project tag?
The OpenGL Error tracker used to collect bugs in graphics drivers or cards:
Hi,
nore...@git.blender.org (2013-11-18 at 0307.44 +):
Commit: 4ea79fcdda6523faf875128ef3d6e8a8ecff67c9
Author: Joshua Leung
Date: Mon Nov 18 16:06:31 2013 +1300
http://developer.blender.org/rB4ea79fcdda6523faf875128ef3d6e8a8ecff67c9
Patch T37363: Highlight bone layers with active
Le 17/11/2013 19:36, Julien RIVAUD (_FrnchFrgg_) a écrit :
Hi everyone,
I'd like to give you notice of a somewhat advanced git HOWTO for
people that used previout git mirrors of blender (as the mirror by
jesterKing). The HOWTO is here:
18 matches
Mail list logo
