From: Lin Mac <mkl0301@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to move a big branches to a new base?
Date: Wed, 3 Mar 2010 11:17:38 +0800 [thread overview]
Message-ID: <10d816431003021917p54491088ie290ec47840dfaa2@mail.gmail.com> (raw)
In-Reply-To: <10d816431002251918vf13a5e8uf0396aa861081bcc@mail.gmail.com>
Hi,
Sorry for re-send this again, for this is really important to me and
trouble me a lot. And I've been searching for a long time, but I
didn't found any useful.
Or maybe it's the way I uses branch wrong? Should I always keep a
branch as clean as possible, and use tag for some unused/not often
used branch, to avoid such problem?
Also I doubt whether my last mail reach the mailing list or not.
So, any response welcome, even RTFM (I'm actually reading it....) is
fine, at least let me know it's just a stupid question.....
Best Regards,
Mac Lin
2010/2/26 Lin Mac <mkl0301@gmail.com>:
> 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.
>
> My "dirty" way is to rebase step by step, it takes about 15-20
> rebases, but the branches is somehow complicated, and this seems
> error-prone to me.
>
> Is there a more clean way to do so?
>
> Thanks in advance.
>
> Best Regards,
> Mac Lin
>
next prev parent reply other threads:[~2010-03-03 3:17 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 [this message]
2010-03-03 3:54 ` John Tapsell
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=10d816431003021917p54491088ie290ec47840dfaa2@mail.gmail.com \
--to=mkl0301@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).