From: Junio C Hamano <gitster@pobox.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] contrib/examples/README: warn of obsolescence
Date: Mon, 12 Jan 2009 17:05:44 -0800 [thread overview]
Message-ID: <7viqokf21j.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87fxjoowyp.fsf@jidanni.org> (jidanni@jidanni.org's message of "Tue, 13 Jan 2009 08:45:18 +0800")
jidanni@jidanni.org writes:
> We attempt to give an explanation of the status of the files in this
> directory.
Yeah, that is a good discipline.
They are original scripted implementations, kept primarily for their
reference value to any aspiring plumbing users who want to learn how
pieces can be fit together.
next prev parent reply other threads:[~2009-01-13 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 0:45 [PATCH/RFC] contrib/examples/README: warn of obsolescence jidanni
2009-01-13 1:05 ` Junio C Hamano [this message]
2009-01-13 1:19 ` [PATCH,v2] contrib/examples/README: give an explanation of the status of these files jidanni
2009-01-13 1:48 ` Junio C Hamano
2009-01-13 10:01 ` Thomas Adam
2009-01-13 13:43 ` Andreas Ericsson
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=7viqokf21j.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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;
as well as URLs for NNTP newsgroup(s).