# Git new-feature-branch best practices 2 messages from 2011-09-11 to 2011-09-12. Participants: Zganyaiko Dmitry, Alexey Shumkin. Thread: https://gitlist.dev/t/28359 ## Zganyaiko Dmitry, 2011-09-11 19:31 Subject: Git new-feature-branch best practices Message-ID: <1315769475.2560.39.camel@mamburu> URL: https://gitlist.dev/e/1315769475.2560.39.camel%40mamburu ``` Hi all! I have a question about using branches. For example, I make branch for some experimental feature. After some time I have completed this feature. I'll checkout previous branch and merge this new feature's branch to it. And there is my question. If I know that this feature was implemented very good and _will not be changed lately_, should I remove this new feature branch (because it will be unused)? Is there some best practice what to do in my case? So, should I remove a branch for some new feature after its implementation if I sure that I will not edit this feature's code later? May be, there is answer for my question already and I missed it? ``` ## Alexey Shumkin, 2011-09-12 08:02 Subject: Re: Git new-feature-branch best practices Message-ID: URL: https://gitlist.dev/e/loom.20110912T100134-606%40post.gmane.org In-Reply-To: <1315769475.2560.39.camel@mamburu> ``` take a look http://comments.gmane.org/gmane.comp.version-control.git/181129 ```