From: Paul Sokolovsky <pmiscml@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: git rebase is confused about commits w/o textual changes (e.g. chmod's)
Date: Sat, 28 Sep 2013 02:32:44 +0300 [thread overview]
Message-ID: <20130928023244.1ce16dc5@x34f> (raw)
In-Reply-To: <20130927222807.GA18384@vauxhall.crustytoothpaste.net>
Hello Brian,
On Fri, 27 Sep 2013 22:28:07 +0000
"brian m. carlson" <sandals@crustytoothpaste.net> wrote:
> On Tue, Sep 24, 2013 at 10:56:48PM +0300, Paul Sokolovsky wrote:
> > Hello,
> >
> > git rebase is confused about commits like
> > https://github.com/pfalcon/civetweb/commit/ce8493837bf7676c6d824cdcb1d5e3a7ed476fe1
> > - it stops, telling user to just run rebase --continue. I remember
[]
>
> I'm interested in solving this, but I can't seem to reproduce it with
> the following script. Can you provide more information about which
> branches specifically you were using (as well as which git version)
> so I can reproduce the problem and look into fixing it?
Thanks for your reply - I wondered if my message went thru (I'm not
subscribed to the list). I'm running:
$ git --version
git version 1.8.4
Specifically from Ubuntu PPA:
http://ppa.launchpad.net/git-core/ppa/ubuntu
Script to reproduce the issue is:
https://gist.github.com/pfalcon/6736632 , based on a real-world case of
merging histories of a fork created from a flat tree snapshot with
the original project it was created from.
Thanks,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2013-09-27 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 19:56 git rebase is confused about commits w/o textual changes (e.g. chmod's) Paul Sokolovsky
2013-09-27 22:28 ` brian m. carlson
2013-09-27 23:32 ` Paul Sokolovsky [this message]
2013-10-04 20:28 ` brian m. carlson
2013-10-04 20:45 ` Paul Sokolovsky
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=20130928023244.1ce16dc5@x34f \
--to=pmiscml@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).