From: Junio C Hamano gits...@pobox.com
I think this is to be expected for git rebase, as it does not even
look at merges. It is a way to find non-merge commits that haven't
been applied yet, and apply them to the upstream to create a new
linear history.
I disagree. git rebase is not
Dale Worley wor...@c-66-31-108-177.hsd1.ma.comcast.net writes:
From: Junio C Hamano gits...@pobox.com
I think this is to be expected for git rebase, as it does not even
look at merges. It is a way to find non-merge commits that haven't
been applied yet, and apply them to the upstream to
From: Junio C Hamano gits...@pobox.com
Sent: Tuesday, March 05, 2013 9:35 PM
Dale Worley wor...@c-66-31-108-177.hsd1.ma.comcast.net writes:
From: Junio C Hamano gits...@pobox.com
I think this is to be expected for git rebase, as it does not even
look at merges. It is a way to find non-merge
Philip Oakley philipoak...@iee.org writes:
Given that many folk appear to trip up with their rebase mindset, does
this suggest that a few tweaks to the manual may be in order to stop
such misunderstandings?
Perhaps.
--
To unsubscribe from this list: send the line unsubscribe git in
the body
(git version 1.7.7.6)
I've been learning how to use Git. While exploring git rebase, I've
discovered that if the branch being rebased contains an evil merge,
that is, a merge which contains changes that are in addition to the
changes in any of the parent commits, the rebase operation will
Junio C Hamano gits...@pobox.com writes:
wor...@alum.mit.edu (Dale R. Worley) writes:
(git version 1.7.7.6)
I've been learning how to use Git. While exploring git rebase, I've
discovered that if the branch being rebased contains an evil merge,
that is, a merge which contains changes that
Thomas Rast tr...@student.ethz.ch writes:
Junio C Hamano gits...@pobox.com writes:
wor...@alum.mit.edu (Dale R. Worley) writes:
(git version 1.7.7.6)
I've been learning how to use Git. While exploring git rebase, I've
discovered that if the branch being rebased contains an evil merge,
7 matches
Mail list logo
