From: Junio C Hamano <gitster@pobox.com>
To: "Tim Harper" <timcharper@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: pre-rebase safety hook
Date: Thu, 04 Dec 2008 14:29:52 -0800 [thread overview]
Message-ID: <7vd4g7d15r.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vbpvrens3.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 04 Dec 2008 11:35:56 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> If you want to prevent a branch whose tip commit is on more than one
> branches from being rebased, I think something like this would suffice.
>
> #!/bin/sh
> LF='
> '
> in_branches=$(git branch -a --with "${2-HEAD}")
> case "$in_branches" in
> *"$LF"*)
> : this commit is on more than two branches
> exit 1
> ;;
> esac
> exit 0
>
> But I didn't test it.
Actually, the above cannot possibly be right. To decide whether to allow
rebasing of a branch or not, you need to also give it from which commit
the rebase will rewrite.
For example, suppose you have a branch "topic", that was forked from
"master" and built two commits, then another branch "side" was forked from
that, and you have three more commits on "topic" since then:
o "side"
/
A---B---C---D---E "topic"
/
---o---o---o---o "master"
Now, can I allow you to rebase "topic"? It depends. These should be
allowed:
git rebase B "topic"
git rebase C "topic"
git rebase D "topic"
but rebasing "topic" on top of "master", or anything that changes the fact
that "topic" contains commits A and B, should be prohibited, because it
will interfere with "side". For example,
git rebase A "topic"
would make this history:
B---o "side"
/
A---B'--C'--D'--E' "topic"
/
---o---o---o---o "master"
where B' and B are different commits.
So you need to check all the commits that will be affected by the rebase
to see if any of them is on a branch other than the one that is being
rebased. The set of commits that needs to be checked are:
git rev-list "$1..${2-HEAD}"
so a naive implementation that is based on brnach --with would probably
look like:
#!/bin/sh
: allow rebasing a detached HEAD
git symbolic-ref -q HEAD || exit 0
LF='
'
git rev-list "$1..${2-HEAD}" |
while read commit
do
case "$(git branch -a --with $commit)" in
*"$LF"*)
: this is on two or more branches
exit 1
;;
esac
done
prev parent reply other threads:[~2008-12-04 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 17:58 pre-rebase safety hook Tim Harper
2008-12-04 19:35 ` Junio C Hamano
2008-12-04 22:29 ` Junio C Hamano [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=7vd4g7d15r.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=timcharper@gmail.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).