From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Jonas Fonseca <fonseca@diku.dk>
Cc: Petr Baudis <pasky@ucw.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Cogito documentation updates
Date: 23 Nov 2005 06:33:10 -0800 [thread overview]
Message-ID: <8664qjph7d.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20051123121651.GB19302@diku.dk>
>>>>> "Jonas" == Jonas Fonseca <fonseca@diku.dk> writes:
Jonas> Ah, yes. I just recently tried local cloning on a FreeBSD box and it
Jonas> worked fine (apart from it spitting out a few errors, see the log below)
Jonas> and since the caveat section only mentioned the -u option I thought
Jonas> everything was fine. However, cloning a specific branch hits the error.
Jonas> So maybe the caveat section should just be updated to say that the -d
Jonas> option is required.
But instead of targeting GNU tools, why not target POSIX tools where
possible?
I realize I'm being a rebel here. I want to use git on non-Linux platforms.
I believe git is useful for far more than Linux Kernel development, and
you're this --> <-- close to making it work.
Delete the -d switch, or explain to me why it is there, and let's work
out a POSIX workaround.
I'm not asking for everyone to be cautious when contributing code.
I'll be happy to be "mr portability" and figure out how to make it
still work on OpenBSD and Darwin (my two platforms of choice).
However, as I said in another posting, maybe I just need to understand
the target market first. (I realize that goal #1 is Linux Kernel
development.)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-11-23 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 10:11 [PATCH] Cogito documentation updates Jonas Fonseca
2005-11-20 15:37 ` Randal L. Schwartz
2005-11-23 12:16 ` Jonas Fonseca
2005-11-23 14:33 ` Randal L. Schwartz [this message]
2005-11-23 14:58 ` Andreas Ericsson
2005-11-23 19:52 ` Junio C Hamano
2005-11-23 17:29 ` Linus Torvalds
2005-11-27 15:28 ` Petr Baudis
2005-11-26 19:12 ` Jonas Fonseca
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=8664qjph7d.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).