From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: Junio C Hamano <gitster@pobox.com>,
Alex Riesen <raa.lkml@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2010, #06; Wed, 24)
Date: Fri, 26 Mar 2010 06:47:07 +0100 [thread overview]
Message-ID: <fcaeb9bf1003252247x339e7fb2y1b714b018c04afef@mail.gmail.com> (raw)
In-Reply-To: <25yNvbuAivZlBuEJoRhXtfoEc7HEZorM5qOrwgQKk7FER_fdzljyMQ@cipher.nrlssc.navy.mil>
On Thu, Mar 25, 2010 at 5:27 PM, Brandon Casey
<brandon.casey.ctr@nrlssc.navy.mil> wrote:
> On 03/25/2010 10:11 AM, Nguyen Thai Ngoc Duy wrote:
>> 2010/3/25 Junio C Hamano <gitster@pobox.com>:
>>> * ar/config-from-command-line (2010-03-19) 1 commit
>>> - Allow passing of configuration parameters in the command line
>>>
>>> * bc/t5505-fix (2010-03-19) 3 commits
>>> - t/t5505-remote.sh: escape * to prevent interpretation by shell as glob
>>> - t5505: add missing &&
>>> - t5505: remove unnecessary subshell invocations
>
> methinks you were over-aggressive with your cut/paste? I don't think bc/t5505-fix
> contains a strndup. Hopefully, it does not break your build on Solaris.
Yeah. It should have been after ar/config-from-command-line. Made me
wonder why this topic had test fixes..
--
Duy
next prev parent reply other threads:[~2010-03-26 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 0:41 What's cooking in git.git (Mar 2010, #06; Wed, 24) Junio C Hamano
2010-03-25 15:11 ` Nguyen Thai Ngoc Duy
2010-03-25 16:27 ` Brandon Casey
2010-03-25 23:11 ` Alex Riesen
2010-03-26 22:53 ` [PATCH 1/2] Allow passing of configuration parameters in the command line Alex Riesen
2010-03-26 22:56 ` [PATCH 2/2] Use strbufs instead of open-coded string manipulation Alex Riesen
2010-03-26 5:47 ` Nguyen Thai Ngoc Duy [this message]
2010-03-25 15:16 ` What's cooking in git.git (Mar 2010, #06; Wed, 24) Nguyen Thai Ngoc Duy
2010-03-26 2:19 ` Ben Walton
2010-03-26 8:39 ` [PATCH] RPM spec: include bash completion support Ian Ward Comfort
2010-03-26 12:10 ` Ben Walton
2010-03-29 18:17 ` Junio C Hamano
2010-03-26 13:07 ` Julian Phillips
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=fcaeb9bf1003252247x339e7fb2y1b714b018c04afef@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=raa.lkml@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 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).