From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2009, #05; Wed, 26)
Date: Thu, 27 Aug 2009 10:32:46 -0700 [thread overview]
Message-ID: <7vr5uxrwld.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <SW-k_fUnLrE0kFNXSIYgMIc-pexuL5ykWs1ZdvHAo9_LMxe9ggJtCA@cipher.nrlssc.navy.mil> (Brandon Casey's message of "Thu\, 27 Aug 2009 11\:41\:18 -0500")
Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil> writes:
>> This seems to break t9001. Near the tip of 'pu' I have a iffy
>> workaround.
>
> Can you squash this into your 'iffy' workaround to help platforms
> (Solaris 7, IRIX 6.5) without the 'yes' utility?
Not in this form, for two reasons ;-)
(1) t7610-mergetool.sh,also seems to use "yes". Perhaps define something
in test-lib.sh?
(2) The implementation is iffy.
> +yes () {
> + test -n "$*" && y="$*" || y='y'
Shouldn't it be
if test $# = 0
then
y=y
else
y="$*"
fi
so that
yes ""
would give runs of empty lines?
next prev parent reply other threads:[~2009-08-27 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 23:45 What's cooking in git.git (Aug 2009, #05; Wed, 26) Junio C Hamano
2009-08-26 23:49 ` Shawn O. Pearce
2009-08-27 0:10 ` Sverre Rabbelier
2009-08-27 0:12 ` Shawn O. Pearce
2009-08-27 19:48 ` Sverre Rabbelier
2009-08-27 16:41 ` Brandon Casey
2009-08-27 17:32 ` Junio C Hamano [this message]
2009-08-27 18:02 ` Brandon Casey
2009-08-28 22:32 ` [PATCH master] t/test-lib.sh: provide a shell implementation of the 'yes' utility Brandon Casey
2009-08-30 1:46 ` What's cooking in git.git (Aug 2009, #05; Wed, 26) Daniel Barkalow
2009-08-30 4:06 ` Junio C Hamano
2009-08-30 20:31 ` Junio C Hamano
2009-08-31 17:06 ` Daniel Barkalow
2009-08-31 23:35 ` Junio C Hamano
2009-09-01 4:18 ` Daniel Barkalow
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=7vr5uxrwld.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--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 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.