git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Tapsell <johnflux@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to move a big branches to a new base?
Date: Wed, 3 Mar 2010 03:54:23 +0000	[thread overview]
Message-ID: <43d8ce651003021954o1411efd2i1a1f26e9b8ed5d54@mail.gmail.com> (raw)
In-Reply-To: <10d816431002251918vf13a5e8uf0396aa861081bcc@mail.gmail.com>

On 26 February 2010 03:18, Lin Mac <mkl0301@gmail.com> wrote:
> Hi,
>
> I have a branch that have about 10 descendent branches. Now I would
> like to move this branch, and all the descendent branches, to a new
> base, and I might need to do so quiet frequently before I merge it to
> master branch.

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.

John

  parent reply	other threads:[~2010-03-03  3:54 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 [this message]
2010-03-04  9:34   ` Lin Mac

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=43d8ce651003021954o1411efd2i1a1f26e9b8ed5d54@mail.gmail.com \
    --to=johnflux@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;
as well as URLs for NNTP newsgroup(s).