From: Junio C Hamano <gitster@pobox•com>
To: jongman.heo@samsung•com
Cc: Jeff King <peff@peff•net>, Thomas Rast <trast@student•ethz.ch>,
git <git@vger•kernel.org>, Antoine Pelisse <apelisse@gmail•com>
Subject: Re: Segmentation fault with latest git (070c57df)
Date: Thu, 31 Jan 2013 17:40:02 -0800 [thread overview]
Message-ID: <7vmwvodd71.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <15540714.372461359682286477.JavaMail.weblogic@epml08> ("허종만"'s message of "Fri, 01 Feb 2013 01:31:27 +0000 (GMT)")
허종만 <jongman.heo@samsung•com> writes:
> But usually when I build upstream Linux kernel, I don't do "make
> clean" after git pull.. I didn't expect that I needed "make
> clean" for git build.
We don't expect anybody need "make clean", either. There is
something wrong in the dependency.
next prev parent reply other threads:[~2013-02-01 1:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 1:31 Re: Segmentation fault with latest git (070c57df) 허종만
2013-02-01 1:40 ` Junio C Hamano [this message]
2013-02-01 6:36 ` Jeff King
2013-02-01 7:06 ` Jeff King
2013-02-01 7:09 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2013-02-04 2:18 Re: Re: Re: " Jongman Heo
2013-02-04 3:40 ` Jonathan Nieder
2013-01-31 7:27 Jongman Heo
2013-01-31 7:55 ` Jeff King
2013-01-31 8:42 ` Thomas Rast
2013-01-31 8:54 ` Jeff King
2013-01-31 1:35 Jongman Heo
2013-01-31 6:49 ` Jeff King
2013-01-31 7:02 ` Antoine Pelisse
2013-01-31 7:35 ` Jeff King
2013-02-04 6:58 ` Jongman Heo
2013-02-04 7:13 ` Junio C Hamano
2013-02-04 8:37 ` Jeff King
2013-02-04 9:16 ` Junio C Hamano
2013-02-04 9:29 ` Junio C Hamano
2013-02-04 9:45 ` Jeff King
2013-02-04 9:38 ` Jeff King
2013-02-04 16:46 ` Junio C Hamano
2013-02-04 18:34 ` Jonathan Nieder
2013-05-15 3:14 ` sam
2013-05-15 3:22 ` sam
2013-05-16 13:12 ` Ramkumar Ramachandra
2013-05-16 13:21 ` Ramkumar Ramachandra
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=7vmwvodd71.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=apelisse@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jongman.heo@samsung$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=trast@student$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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