From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH] Reintegrate script
Date: Mon, 26 Jan 2009 01:03:16 -0800 [thread overview]
Message-ID: <7vd4ea8mnf.fsf@gitster.siamese.dyndns.org> (raw)
In a workflow that uses topic branches heavily, you would need to keep
updating test integration branch(es) all the time. If they are managed
like my 'next' by merging the tips of topics that have grown since the
last integration, it is not so difficult. You only need to review output
from "git branch --no-merged next" to see if there are topics that can and
needs to be merged to 'next'.
But sometimes it is easier to rebuild a test integration branch from
scratch all the time, especially if you do not publish it for others to
build on.
I've been using this script for some time to rebuild jch and pu branches
in my workflow. jch's tip is supposed to always match 'next', but it is
rebuilt from scratch on top of 'master' by merging the same topics that
are in 'next'. You can use the same script in your work.
To use it, you give a commit range base..tip to the script, and you will
see a shell script that uses a series of 'git-merge'. "base" is the more
stable branch that you rebuild your test integration branch on top (in my
case, 'master'), and "tip" is where the tip of the test integration branch
is from the last round (in my case, 'jch' or 'pu').
Then you can run the resulting script, fix conflicted merge and use
'git-commit', and then repeat until all the branches are re-integrated on
top of the base branch.
$ Meta/Reintegrate master..jch >/var/tmp/redo-jch.sh
$ cat /var/tmp/redo-jch.sh
#!/bin/sh
while read branch eh
do
case "$eh" in
"") git merge "$branch" || break ;;
?*) echo >&2 "Eh? $branch $eh"; break ;;
esac
done <<EOF
jc/blame
js/notes
ks/maint-mailinfo-folded~3
tr/previous-branch
EOF
$ git checkout jch
$ git reset --hard master
$ /var/tmp/redo-jch.sh
... if there is conflict, resolve, "git commit" here ...
$ /var/tmp/redo-jch.sh
... repeat until everything is applied.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
* This is taken from my 'todo' branch, which I keep a checkout in Meta/
directory.
Reintegrate | 42 ++++++++++++++++++++++++++++++++++++++++++
1 files changed, 42 insertions(+), 0 deletions(-)
create mode 100755 Reintegrate
diff --git a/Reintegrate b/Reintegrate
new file mode 100755
index 0000000..dfdb73e
--- /dev/null
+++ b/Reintegrate
@@ -0,0 +1,42 @@
+#!/bin/sh
+
+merge_msg="Merge branch '\(.*\)'"
+x40='[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]'
+x40="$x40$x40$x40$x40$x40$x40$x40$x40"
+LF='
+'
+
+echo '#!/bin/sh
+while read branch eh
+do
+ case "$eh" in
+ "") git merge "$branch" || break ;;
+ ?*) echo >&2 "Eh? $branch $eh"; break ;;
+ esac
+done <<EOF'
+
+git log --pretty=oneline --first-parent "$1" |
+{
+ series=
+ while read commit msg
+ do
+ other=$(git rev-parse --verify "$commit^2") &&
+ branch=$(expr "$msg" : "$merge_msg") &&
+ tip=$(git rev-parse --verify "refs/heads/$branch" 2>/dev/null) &&
+ merged=$(git name-rev --refs="refs/heads/$branch" "$other" 2>/dev/null) &&
+ merged=$(expr "$merged" : "$x40 \(.*\)") &&
+ test "$merged" != undefined || {
+ other=$(git log -1 --pretty='format:%s' $other) &&
+ merged="$branch :rebased? $other"
+ }
+ if test -z "$series"
+ then
+ series="$merged"
+ else
+ series="$merged$LF$series"
+ fi
+ done
+ echo "$series"
+}
+
+echo 'EOF'
--
1.6.1.1.248.g7f6d2
next reply other threads:[~2009-01-26 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 9:03 Junio C Hamano [this message]
2009-01-26 11:18 ` [PATCH] Reintegrate script Johannes Schindelin
2009-02-13 18:23 ` [PATCH] Meta/Reintegrate: Record all merges to prevent losing topics Bernt Hansen
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=7vd4ea8mnf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.