From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: John Keeping <john@keeping.me.uk>
Subject: [ANNOUNCE] git reintegrate 0.1; manager of integration branches
Date: Fri, 1 Nov 2013 06:35:39 -0600 [thread overview]
Message-ID: <CAMP44s2cuHnW0cGEBRt2EmG8Wmav4athMLXRCh2cJ2KymeHmmg@mail.gmail.com> (raw)
Hi,
git reintegrate is a helper tool to manage integration branches, it
has all the options of other known tools.
This is a rewrite of John Keeping's git-integration in Ruby, it has
essentially the same features and passes all the git-integration
tests, but it has other features.
One feature that is missing from git-integration is the ability to
parse existing integration branches.
To give a try you can do:
git clone https://github.com/gitster/git/
cd git
git fetch -u origin 'refs/tags/*:refs/tags/*' 'refs/heads/*:refs/heads/*'
git checkout pu
git reintegrate --generate pu master
Which will generate the integration instructions for you:
% git reintegrate --cat
base master
merge jl/submodule-mv
Moving a regular file in a repository with a .gitmodules file was
producing a warning 'Could not find section in .gitmodules where
path=<filename>'.
merge ap/remote-hg-unquote-cquote
A fast-import stream expresses a pathname with funny characters by
quoting them in C style; remote-hg remote helper forgot to unquote
such a path.
merge jk/for-each-ref-skip-parsing
merge jk/pack-corruption-post-mortem
merge jk/reset-p-current-head-fix
"git reset -p HEAD" has codepath to special case it from resetting
to contents of other commits, but recent change broke it.
...
It also has support for "evil merges", so it should be perfectly
usable for git.git maintenance.
You can edit the instructions with `git reintegrate --edit`.
The simplest way to begin an integration branch is with:
git reintegrate --create pu master
git reintegrate --add=branch1 --add=branch2 --add=branch3
To generate the integration branch run `git reintegrate --rebuild`, if
there are merge conflicts, solve them and continue with `git
reintegrate --continue`.
Despite having more features, the code is actually smaller thanks to
Ruby awesomeness.
Enjoy.
https://github.com/felipec/git-reintegrate
--
Felipe Contreras
next reply other threads:[~2013-11-01 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 12:35 Felipe Contreras [this message]
2013-11-02 11:00 ` [ANNOUNCE] git reintegrate 0.1; manager of integration branches John Keeping
2013-11-02 11:18 ` Felipe Contreras
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=CAMP44s2cuHnW0cGEBRt2EmG8Wmav4athMLXRCh2cJ2KymeHmmg@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/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).