* Git new-feature-branch best practices
@ 2011-09-11 19:31 Zganyaiko Dmitry
2011-09-12 8:02 ` Alexey Shumkin
0 siblings, 1 reply; 2+ messages in thread
From: Zganyaiko Dmitry @ 2011-09-11 19:31 UTC (permalink / raw)
To: git
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Git new-feature-branch best practices
2011-09-11 19:31 Git new-feature-branch best practices Zganyaiko Dmitry
@ 2011-09-12 8:02 ` Alexey Shumkin
0 siblings, 0 replies; 2+ messages in thread
From: Alexey Shumkin @ 2011-09-12 8:02 UTC (permalink / raw)
To: git
take a look
http://comments.gmane.org/gmane.comp.version-control.git/181129
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-09-12 8:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-11 19:31 Git new-feature-branch best practices Zganyaiko Dmitry
2011-09-12 8:02 ` Alexey Shumkin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).