From: John Keeping <john@keeping.me.uk>
To: Larry Minton <larry.minton@autodesk.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Is there a way to have local changes in a branch 'bake' while working in different branches?
Date: Fri, 16 Dec 2016 15:22:27 +0000 [thread overview]
Message-ID: <20161216152227.GA1783@john.keeping.me.uk> (raw)
In-Reply-To: <14b481f95c5043aca6cdfddfe4728fa9@BLUPR79MB001.MGDADSK.autodesk.com>
On Thu, Dec 15, 2016 at 08:14:58PM +0000, Larry Minton wrote:
> My question:
>
> Let's say I have a code change that I want to 'bake' for a while
> locally, just to make sure some edge case doesn't pop up while I am
> working on other things. Is there any practical way of doing that? I
> could constantly merge that 'bake me' branch into other branches as I
> work on them and then remove those changes from the branches before
> sending them out for code review, but sooner or later pretty much
> guaranteed to screw that up....
I wrote a tool [1] a while ago to manage integration branches so I use a
personal integration branch to pull together various in-progress
branches.
It means you can keep each topic in its own branch but work/test on top
of a unified branch by running:
git integration --rebuild my-integration-branch
whenever you change one of the topic branches.
I also use the instruction sheet to keep track of abandoned topics that
I might want to go back to but which are currently in a broken state,
you can see an example of that in my CGit integration branch [2].
[1] http://johnkeeping.github.io/git-integration/
[2] https://github.com/johnkeeping/cgit/blob/d01ce31ed3dfa9b05ef971464da2af5b9d6f2756/GIT-INTEGRATION-INSN
prev parent reply other threads:[~2016-12-16 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 20:14 Is there a way to have local changes in a branch 'bake' while working in different branches? Larry Minton
2016-12-15 22:44 ` Aaron Schrab
2016-12-16 0:07 ` Junio C Hamano
2016-12-16 15:22 ` John Keeping [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=20161216152227.GA1783@john.keeping.me.uk \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=larry.minton@autodesk.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).