[Bf-committers] Git migration: branches to exclude

[Campbell Barton]

On Sun, Nov 3, 2013 at 3:08 AM, walid shouman
<eng.walidshouman at gmail.com> wrote:
> soc-2013-meshdata_transfer is under active developement and isnt so far
> from being finished and merged.

I'd consider this a special case, the branch was created, a lot of
work was done, then removed and redone - the history has a lot of
noise.

Most of the work is in one file which is currently quite small (~500
LOC), so I think this can be committed as a patch and its no big deal
if the history for each rev isn't maintained.

> On Nov 2, 2013 5:29 PM, "Campbell Barton" <ideasman42 at gmail.com> wrote:
>>
>> Heres my first pass at listing branches to exclude,
>>
>> On the wiki page there are some details about why branches are
>> selected to be excluded.
>>
>>
> http://wiki.blender.org/index.php/Dev:Ref/Proposals/MigrationToGit#Branches_to_Exclude
>>
>>
>> If you rather your branch is included, reply to this mail - but keep
>> in mind this means blenders git repository will increase in size and
>> everyone who checks out Blender will (by default) be downloading the
>> branch too.
>> So if this is project from years ago that was never merged, we better
>> just keep the subversion as an archive.
>>
>> (rough guess - if we include all branches the repository would
>> increase from 260mb to 600-800mb)
>> ... but I cant test this, my system runs out of memory creating a git
>> repo with all branches.
>>
>> --
>> - Campbell
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers



-- 
- Campbell