From: Mike McCormack <mike@codeweavers.com>
To: git@vger.kernel.org
Subject: git rebase behaviour changed?
Date: Tue, 17 Jan 2006 12:49:50 +0900 [thread overview]
Message-ID: <43CC695E.2020506@codeweavers.com> (raw)
Hi,
git-rebase was a very useful tool for me to help organize my patches.
Recently, it seems the behaviour of git-rebase changed. It used to take
the commits I'd made to my "master" branch and reapply them to a new
"master" branch on top of "origin". Where rebase from git-0.99.x used
to work, git-1.1.3 now does nothing and gives me the following message:
git-rebase origin
-> Current branch refs/heads/master is up to date.
However, I can do the "rebase" manually with:
git branch master-20060117
git reset --hard origin
git-format-patch -k --stdout --full-index origin master-20060117 | \
git am --binary -3 -k
Is this broken, or am I meant to be doing something different now?
thanks,
Mike
next reply other threads:[~2006-01-17 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 3:49 Mike McCormack [this message]
2006-01-17 5:50 ` git rebase behaviour changed? Junio C Hamano
2006-01-17 6:08 ` Mike McCormack
2006-01-17 6:29 ` Junio C Hamano
2006-01-17 6:52 ` Martin Langhoff
2006-01-17 8:11 ` Junio C Hamano
2006-01-17 8:33 ` Martin Langhoff
2006-01-17 8:43 ` Junio C Hamano
2006-01-17 8:56 ` Junio C Hamano
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=43CC695E.2020506@codeweavers.com \
--to=mike@codeweavers.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).