From: Junio C Hamano <gitster@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tay Ray Chuan <rctay89@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Ali Polatel <polatel@gmail.com>,
git@vger.kernel.org
Subject: Re: git clone http://git.savannah.gnu.org/cgit/xboard.git segfaults
Date: Fri, 28 Aug 2009 18:10:48 -0700 [thread overview]
Message-ID: <7vprafzap3.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7v8wh35tl8.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Fri\, 28 Aug 2009 17\:53\:07 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Nobody can expect me to keep track of everything; the final "Here is the
> good one" would help the process flow smoothly and reduce the chance of
> mistakes.
I forgot to add...
In this case, it is _now_ clear to me that you consider your
Subject: Re: git clone http://git.... segfaults
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ali Polatel <polatel@gmail.com>, git@vger.kernel.org
Date: Wed, 26 Aug 2009 20:20:53 +0800
Message-ID: <20090826202053.6e6442a6.rctay89@gmail.com>
to be the final version, so I'd just add "noticed by Ali Polatel who later
tested this patch to verify; Dscho helped to identify the problem spot."
at the end of the commit log message in the message and apply. IOW, no
need to resend.
Ali's original report is about 1.6.4 so I presume this is 'maint'
material, so let's include this in 1.6.4.2.
next prev parent reply other threads:[~2009-08-29 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 13:56 git clone http://git.savannah.gnu.org/cgit/xboard.git segfaults Ali Polatel
2009-08-17 14:17 ` Johannes Schindelin
2009-08-17 14:22 ` Johannes Schindelin
2009-08-26 12:20 ` Tay Ray Chuan
2009-08-26 13:12 ` Ali Polatel
2009-08-27 7:39 ` Johannes Schindelin
2009-08-29 0:07 ` Tay Ray Chuan
2009-08-29 0:53 ` Junio C Hamano
2009-08-29 1:10 ` Junio C Hamano [this message]
2009-08-29 2:03 ` Tay Ray Chuan
2009-08-17 14:40 ` Lars Hjemli
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=7vprafzap3.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=polatel@gmail.com \
--cc=rctay89@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.