From: Zganyaiko Dmitry <zdo.str@gmail.com>
To: git@vger.kernel.org
Subject: Git new-feature-branch best practices
Date: Sun, 11 Sep 2011 22:31:15 +0300 [thread overview]
Message-ID: <1315769475.2560.39.camel@mamburu> (raw)
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?
next reply other threads:[~2011-09-11 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 19:31 Zganyaiko Dmitry [this message]
2011-09-12 8:02 ` Git new-feature-branch best practices Alexey Shumkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1315769475.2560.39.camel@mamburu \
--to=zdo.str@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox