From: Thomas Rast <trast@student.ethz.ch>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: git rebase orthodontics
Date: Wed, 7 Jan 2009 17:31:04 +0100 [thread overview]
Message-ID: <200901071731.20343.trast@student.ethz.ch> (raw)
In-Reply-To: <87sknvxje8.fsf@jidanni.org>
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
jidanni@jidanni.org wrote:
> wherein he discovers there are no guard rails
Good thing you learned this before getting to git-reset.
> $ EDITOR=cat git rebase --interactive master
> pick 07aef4a This is a commit with No files, wow. bla.
> # Rebase 3ad166e..07aef4a onto 3ad166e ...
> Successfully rebased and updated refs/heads/jidanni.
> (But it didn't. git show shows no change. ls -l shows
> refs/heads/jidanni was not touched.
> OK, it seems like all I am doing is changing
> A jidanni
> /
> D---E---F---G master
> into the same thing, a noop. But shouldn't it warn and quit, instead
> of rewarding me with the success message?
You asked for an interactive rebase of the range master..jidanni,
which consists of A, so it gave you an editor offering 'pick A' and
the chance to change that.
Non-interactive rebase indeed checks if you attempt to rebase, but are
already up to date. Interactive doesn't; the assumption is that
interactive rebases aren't used "blindly" to update. (Rebasing
changes committer and commit time, so there is a difference between
not rebasing at all, and merely ending up with the same history.)
> Let's try it the other way
> around:
> $ git checkout master
> $ git rebase --interactive jidanni #Wherein one sees:
> noop
> # Rebase 07aef4a..3ad166e onto 07aef4a
> Successfully rebased and updated refs/heads/master.
> OK, now I have achieved
> D---E---F---G---A master, jidanni
> Observations:
> When I tried a noop, it didn't say noop in the editor.
> When I tried a yesop, it did say noop in the editor.
The 'noop' means that there are no commits in the range you asked to
rebase, which is jidanni..master. It's telling you that it is going
to update the branch pointer, but not carry over any of the commits.
This can happen even if jidanni..master is nonempty, but all commits
in it are already contained in jidanni.
> In both cases it gave the same success message.
It successfully did what you told it to do.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-01-07 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:47 git rebase orthodontics jidanni
2009-01-07 16:10 ` Boyd Stephen Smith Jr.
2009-01-07 16:31 ` Thomas Rast [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=200901071731.20343.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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).