From: Len Brown <lenb@kernel.org>
To: git@vger.kernel.org
Subject: Segmentation fault git read-tree
Date: Thu, 13 Mar 2008 23:59:06 -0400 [thread overview]
Message-ID: <200803132359.06745.lenb@kernel.org> (raw)
i pushed the branches necessary to reproduce this right
before it happened, so you should be able to pull them
and try it yourself.
thanks,
-Len
[lenb@t61 acpi (test)]$ git push lenb
lenb@master.kernel.org's password:
Counting objects: 723, done.
Compressing objects: 100% (237/237), done.
Writing objects: 100% (492/492), 82.22 KiB, done.
Total 492 (delta 389), reused 337 (delta 249)
To master.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git
93d7446..dba92d3 linus -> linus
93d7446..dba92d3 release -> release
93d7446..c68a500 suspend -> suspend
93d7446..5dceb6d test -> test
[lenb@t61 acpi (test)]$ git merge test suspend
Already up-to-date with 5dceb6d3377c3cbd06f7b3282fec0e201273c302
Trying simple merge with c68a5009ab9938af22af668e0e2d646d2482c866
/home/lenb/bin/git-merge-octopus: line 52: 24287 Segmentation fault git read-tree -u -m --aggressive $common $MRT $SHA1
Merge with strategy octopus failed.
[lenb@t61 acpi (test)]$ git merge test suspend
fatal: unable to create '.git/index.lock': File exists
Already up-to-date with 5dceb6d3377c3cbd06f7b3282fec0e201273c302
Trying simple merge with c68a5009ab9938af22af668e0e2d646d2482c866
fatal: unable to create '.git/index.lock': File exists
Merge with strategy octopus failed.
[lenb@t61 acpi (test)]$ git --version
git version 1.5.4.4.537.gb75aa
[lenb@t61 acpi (test)]$
next reply other threads:[~2008-03-14 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 3:59 Len Brown [this message]
2008-03-14 4:26 ` Segmentation fault git read-tree Linus Torvalds
2008-03-14 4:30 ` Linus Torvalds
2008-03-14 4:37 ` Segmentation fault in " Linus Torvalds
2008-03-14 4:44 ` Junio C Hamano
2008-03-14 4:48 ` Junio C Hamano
2008-03-14 5:07 ` Junio C Hamano
2008-03-14 18:24 ` Len Brown
2008-03-14 17:37 ` Linus Torvalds
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=200803132359.06745.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=git@vger.kernel.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).