Git new-feature-branch best practices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]