From: Lin Mac <mkl0301@gmail.com>
To: John Tapsell <johnflux@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to move a big branches to a new base?
Date: Thu, 4 Mar 2010 17:34:12 +0800 [thread overview]
Message-ID: <10d816431003040134j103c567if10aacf0fa10701f@mail.gmail.com> (raw)
In-Reply-To: <43d8ce651003021954o1411efd2i1a1f26e9b8ed5d54@mail.gmail.com>
2010/3/3 John Tapsell <johnflux@gmail.com>:
> I tend to keep my branches as small as possible - a few commits at
> most. And avoid merges like the plague. This seems to work pretty
> well.
> Remember you can squash your commits together to keep the branches
> clean and well-ordered.
squash is a powerful tools, but doens't help much in this situation.
In other word, one have to prevent a branch to becoming a tree.
Does it worth to have a new tool for such situation?
Best Regard,
Mac Lin
prev parent reply other threads:[~2010-03-04 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 3:18 How to move a big branches to a new base? Lin Mac
2010-03-03 3:17 ` Lin Mac
2010-03-03 3:54 ` John Tapsell
2010-03-04 9:34 ` Lin Mac [this message]
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=10d816431003040134j103c567if10aacf0fa10701f@mail.gmail.com \
--to=mkl0301@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).