Re: [Bf-committers] Introduction

Hi there, welcome! Please find introduction to new developers at [1]. Also, at [2], you can see suggested ideas, for this year as well as older ones. Find us on chat [3] too! Cheers Ankit [1]: https://wiki.blender.org/wiki/Developer_Intro [2]: ht

Re: [Bf-committers] Gsoc advices

Hi! If you might need to clear some doubts about the code or design, chat is good. If a detailed discussion is needed, post on devtalk.blender.org under Summer of code subtopic. [1] These developers would have good advices for the said project. Finalised proposal would indeed be submitted on

Re: [Bf-committers] Blender developer meeting notes - 2020.4.6

Hi ! > Google Summer of Code > = > * The students' proposals are currently under review (until January 31st). until April 30th * ? https://summerofcode.withgoogle.com/how-it-works/#timeline > * Mentors to start r

[Bf-committers] Proposal: Add a git blame ignore file to the repo.

Hey all! Git 2.23 introduced `--ignore-rev ` option to ignore revisions and `--ignore-revs-file ` to do so in bulk. [1] [2] D9234 proposes adding a file to the repo to list commits, for which the committer does not deserve to be blamed. An initial list is there in the file, one may remember some

Re: [Bf-committers] Wiki Account

Hi Top right > Create Design: https://developer.blender.org/maniphest/ See other design tasks: https://developer.blender.org/maniphest/query/UuLbRqWQHCIm/#R Wiki doc: https://wiki.blende

Re: [Bf-committers] Proposal: Add a git blame ignore file to the repo.

Hello The revision D9234 [1] has been committed [2]. The Tools/Git wiki page [3] has also been updated. Please note a correction in the commands in the trailing mail: the file has been renamed from `.gitblame-ignore-revs` to `.git-blame-ignore-revs`. Cheers! Ankit Meel [1] https://developer.ble

Re: [Bf-committers] .git-blame-ignore-revs entries.

Hello I'm getting used to it. I'll remove several commits soon, now that I have received the feedback on the last commit, and will use stricter conditions in the future. My premise - for being lenient was that it saves other people from committing to the file which keeps the noise in git log lo

Re: [Bf-committers] .git-blame-ignore-revs entries.

- Several smaller commits should be added to this list at once, >> because >>>> adding >>>> # one extra commit (to edit this file) after every small cleanup is >>> noisy. >>>> >>>> Note that only massive or automated changes ar

Re: [Bf-committers] Clang-Tidy: Request for Feedback

Consider `clang-tidy-diff.py` and `run-clang-tidy.py` [1] to cut down time to run clang-tidy further. The latter is not incremental though. Editor extensions based on clangd + LSP can show clang-tidy violations live as the file is being edited. I've tried [2] and it's fine. There's one for VSCode

Re: [Bf-committers] *** RESPECTFULLY NOT SPAM *** Weekly Development Notes Followup

Hi And now, in what case is it acceptable to mark an email asking about such an issue as spam? That is very likely a false positive by some email filter, and not anything Bastien did. Ankit On 24/09/21 11:29, Ryan Inch via Bf-committers wrote: Thanks for your quick reply Bastian.  My email

Re: [Bf-committers] move prebuilt libs from svn to git?

Tom: 1. Unlike SVN checkout, git checkout cannot be resumed. It starts over if interrupted. 2. .git folder's size will blow up with every release. Git is not so good for binary files. Chad: https://developer.blender.org/T73511 https://developer.blender.org/T73394 Cheers Ankit On 17/06/22

Re: [Bf-committers] move prebuilt libs from svn to git?

Zack - To track library versions https://developer.blender.org/T88438 - To tag corresponding versions for each release https://svn.blender.org/svnroot/bf-blender/tags/ - Some bugs show up due to deps also, https://developer.blender.org/rBL62677 . VCS can point to the commit that caused it. An