[Soc-2017-dev] vertex paint project - ply exporter

Howard Trickey howard.trickey at gmail.com
Mon Jul 10 14:10:00 CEST 2017


Darshan,

I think it is because the addons subdirectory of blender/release/scripts is
registered as a submodule (see https://git-scm.com/docs/git-submodule )
while the startup one is not.

On Mon, Jul 10, 2017 at 7:57 AM Darshan kadu <darsh7807 at gmail.com> wrote:

> Hii, Mr. Howard,
>
> I have made changes in the blender\release\scripts\addons\io_mesh_ply,
> don't know what is happening,
> When made changes to the blender\release\scripts\startup\bl_ui dir they
> got committed.
>
>
> On Mon, Jul 10, 2017 at 5:10 PM, Howard Trickey <howard.trickey at gmail.com>
> wrote:
>
>> Hey Darshan and other mentors:
>>
>> Darhsan, your last commit comment said that it committed changes to the
>> ply exporter, but it did not. I think you may have been making the changes
>> in the copy of the exporter that is in your bin directory. Or maybe in the
>> release directory of blender, and then it gets copied into your bin when
>> you make install (?)
>>
>> The actualy real place the exporters is stored is the separate git
>> repository blender-addons that is a subproject of blender. I think stuff
>> from there overwrites your release directory when/if you do git submodule
>> foreach git pull origin master.
>>
>> Other mentors:
>> what is the proper procedure to follow for a gsoc project that wants to
>> change something in addons? Should a branch of addons be made to go along
>> with soc-2017-vertex_paint?
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/soc-2017-dev/attachments/20170710/f27cc54c/attachment.htm 


More information about the Soc-2017-dev mailing list