Git development
 help / color / mirror / Atom feed
From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: torvalds@osdl.org
Cc: cw@f00f.org, junkio@cox.net, git@vger.kernel.org,
	yoshfuji@linux-ipv6.org
Subject: Re: Make "git-ls-files" work in subdirectories
Date: Mon, 22 Aug 2005 08:50:19 +0900 (JST)	[thread overview]
Message-ID: <20050822.085019.32290547.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0508211613340.3317@g5.osdl.org>

In article <Pine.LNX.4.58.0508211613340.3317@g5.osdl.org> (at Sun, 21 Aug 2005 16:17:52 -0700 (PDT)), Linus Torvalds <torvalds@osdl.org> says:

> getopt() is too limited, and getopt_long() is very glibc-specific and thus
> inherently evil. And the complexity of doing autoconf or similar is worse
> than just doing it by hand.

(I'm not against having our own getopt_long()
or alike, but anyway...)

Well, not really "glibc-specific" now.

NetBSD (>=1.5) has thir own implementation of getopt_long()
(w/ 4-clause BSD licence, which is not compatible w/ GPL2).
OpenBSD (>=3.3), FreeBSD (>=5.0), too.
Solaris (>=9?) seems to have one, too.

NetBSD: http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/stdlib/getopt_long.c
OpenBSD: http://www.openbsd.org/cgi-bin/cvsweb.cgi/src/lib/libc/stdlib/getopt_long.c
FreeBSD: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/stdlib/getopt_long.c
Solaris: http://iforce.sun.com/protected/solaris10/adoptionkit/general/getopt_long.txt

--yoshfuji

      parent reply	other threads:[~2005-08-21 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 19:55 Make "git-ls-files" work in subdirectories Linus Torvalds
2005-08-21 22:46 ` Chris Wedgwood
2005-08-21 23:17   ` Linus Torvalds
2005-08-21 23:45     ` Chris Wedgwood
2005-08-21 23:50     ` YOSHIFUJI Hideaki / 吉藤英明 [this message]

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=20050822.085019.32290547.yoshfuji@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=cw@f00f.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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