From: Hakim Cassimally <hakim.cassimally@gmail.com>
To: git@vger.kernel.org
Cc: Sam Vilain <sam@vilain.net>
Subject: Re: git-cherry-pick problem - directory not touched by commit is marked "added by us"
Date: Fri, 8 Jan 2010 22:29:12 +0000 [thread overview]
Message-ID: <82cfa8031001081429i58496c8y1775deadc11ab4be@mail.gmail.com> (raw)
In-Reply-To: <7vzl4qegdm.fsf@alter.siamese.dyndns.org>
(woops, sent just to Junio, resending to list)
Hi,
Thanks for the suggestions, I've tried both those commands, and they
break too :-(
2010/1/7 Junio C Hamano <gitster@pobox.com>:
> Junio C Hamano <gitster@pobox.com> writes:
>> What "cherry-pick" internally does is to run:
>>
>> git merge-recursive 301a^ -- HEAD 301a
>>
>> That is, "We are at HEAD; consolidate the change since 301a^ to 301a into
>> our state, and leave the result in the index and the work tree". Then it
>> commits the result. One thing to try is to see if this gives the same
>> kind of breakage.
$ git merge-recursive 301a^ -- HEAD 301a
# woo! no response! promising
$ git status
# On branch cgi_branch
<snip>
# new file: bin/upload_module.pl
#
# Unmerged paths:
# added by us: www/client/css/admin-clean.css
# added by us: www/client/css/admin.css
<snip dozens of spurious "added by us">
> There actually is another possibility; we used to run inside "cherry-pick"
>
> git merge-resolve 301a^ -- HEAD 301a
>
> instead. The request is the same but it uses a different algorithm, so if
> one fails and one succeeds, that might give us a better clue to figure out
> what is going on.
$ git merge-resolve 301a^ -- HEAD 301a
Trying simple merge.
Simple merge failed, trying Automatic merge.
error: www/client: is a directory - add individual files instead
fatal: Unable to process path www/client
error: www/css: is a directory - add individual files instead
fatal: Unable to process path www/css
error: www/images: is a directory - add individual files instead
fatal: Unable to process path www/images
error: www/js: is a directory - add individual files instead
fatal: Unable to process path www/js
fatal: merge program failed
At least the latter fails more informatively?
Thanks again for the help and suggestions ;-)
osfameron
prev parent reply other threads:[~2010-01-08 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 12:33 git-cherry-pick problem - directory not touched by commit is marked "added by us" Hakim Cassimally
2010-01-05 21:37 ` Sam Vilain
2010-01-06 11:28 ` Hakim Cassimally
2010-01-07 3:30 ` Junio C Hamano
2010-01-07 3:35 ` Junio C Hamano
2010-01-08 22:29 ` Hakim Cassimally [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=82cfa8031001081429i58496c8y1775deadc11ab4be@mail.gmail.com \
--to=hakim.cassimally@gmail.com \
--cc=git@vger.kernel.org \
--cc=sam@vilain.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).