From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: git-cherry-pick and git-commit --amend in version 1.7.6.4
Date: Thu, 06 Oct 2011 15:22:56 +0200 [thread overview]
Message-ID: <4E8DABB0.4090206@6wind.com> (raw)
In-Reply-To: <CAG+J_DzY6oW3CgCPDhD81Eue1Ygh+3pR7Q_NZEhauH_qkyUwqQ@mail.gmail.com>
Le 06/10/2011 15:09, Jay Soffian a écrit :
> On Thu, Oct 6, 2011 at 3:37 AM, Nicolas Dichtel
> <nicolas.dichtel@6wind.com> wrote:
>> # ls .git
>> branches COMMIT_EDITMSG config description FETCH_HEAD HEAD hooks
>> index info logs objects ORIG_HEAD packed-refs refs
>
> No CHERRY_PICK_HEAD, so far so good.
>
>> # git cherry-pick 3f78d1f210ff89af77f042ab7f4a8fee39feb1c9
>> [dev 4cca2c2] drivers/net/usb/asix.c: Fix unaligned accesses
>> 1 files changed, 33 insertions(+), 1 deletions(-)
>
> cherry-pick completes successfully.
>
>> # ls .git
>> branches CHERRY_PICK_HEAD COMMIT_EDITMSG config description FETCH_HEAD
>> HEAD hooks index info logs objects ORIG_HEAD packed-refs refs
>
> This is bad. CHERRY_PICK_HEAD should only exist if the cherry-pick failed.
>
> I really don't know what could cause this. Possibly a hook in your repo?
No hooks:
# ls .git/hooks/
applypatch-msg.sample post-commit.sample post-update.sample
pre-commit.sample pre-rebase.sample
commit-msg.sample post-receive.sample pre-applypatch.sample
prepare-commit-msg.sample update.sample
>
> Using "GIT_TRACE=1 git cherry-pick
> 3f78d1f210ff89af77f042ab7f4a8fee39feb1c9" will tell you whether git is
> running any hooks.
Here is the output:
# GIT_TRACE=1 git cherry-pick 3f78d1f210ff89af77f042ab7f4a8fee39feb1c9
trace: built-in: git 'cherry-pick' '3f78d1f210ff89af77f042ab7f4a8fee39feb1c9'
trace: run_command: 'commit' '-n' '-F' '.git/MERGE_MSG'
trace: exec: 'git' 'commit' '-n' '-F' '.git/MERGE_MSG'
setup: git_dir: .git
setup: worktree: /home/dichtel/DEV/linux-2.6
setup: cwd: /home/dichtel/DEV/linux-2.6
setup: prefix: (null)
trace: built-in: git 'commit' '-n' '-F' '.git/MERGE_MSG'
[master 8372873] drivers/net/usb/asix.c: Fix unaligned accesses
1 files changed, 33 insertions(+), 1 deletions(-)
#
>
> I can't think of anything config-wise that would cause this behavior.
With a very basic config, the pb he still here:
cat ~/.gitconfig
[user]
name = Nicolas Dichtel
email = nicolas.dichtel@6wind.com
I will try to do some other tests.
Regards,
Nicolas
next prev parent reply other threads:[~2011-10-06 13:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:52 git-cherry-pick and git-commit --amend in version 1.7.6.4 Nicolas Dichtel
2011-10-05 16:50 ` Jay Soffian
2011-10-06 7:37 ` Nicolas Dichtel
2011-10-06 7:53 ` Nicolas Dichtel
2011-10-06 13:09 ` Jay Soffian
2011-10-06 13:22 ` Nicolas Dichtel [this message]
2011-10-06 13:44 ` Jay Soffian
2011-10-05 17:40 ` Junio C Hamano
2011-10-05 17:43 ` Jay Soffian
2011-10-05 21:55 ` Junio C Hamano
2011-10-05 22:23 ` Jay Soffian
2011-10-05 22:32 ` Junio C Hamano
2011-10-06 0:08 ` Jay Soffian
2011-10-05 23:03 ` Junio C Hamano
2011-10-05 23:42 ` Junio C Hamano
2011-10-06 7:06 ` 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=4E8DABB0.4090206@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=peff@peff.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).