From: Junio C Hamano <junkio@cox.net>
To: Ryan Anderson <ryan@michonline.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH] Use "-script" postfix for scripts
Date: Sat, 13 Aug 2005 01:57:22 -0700 [thread overview]
Message-ID: <7v64uaqknh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050812222716.GD22778@mythryan2.michonline.com> (Ryan Anderson's message of "Fri, 12 Aug 2005 18:27:16 -0400")
Ryan Anderson <ryan@michonline.com> writes:
> See, for example, the history on git-rename-script for why this is good.
Why do you think it is a good example? What happens when next
time somebody rewrites it in C?
next prev parent reply other threads:[~2005-08-13 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 13:28 [PATCH] Use "-script" postfix for scripts Johannes Schindelin
2005-08-12 15:32 ` Junio C Hamano
2005-08-12 16:00 ` Johannes Schindelin
2005-08-12 21:55 ` Linus Torvalds
2005-08-12 22:27 ` Ryan Anderson
2005-08-13 8:57 ` Junio C Hamano [this message]
2005-08-13 16:35 ` Linus Torvalds
2005-08-13 22:25 ` Ryan Anderson
2005-08-13 22:28 ` Petr Baudis
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=7v64uaqknh.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.com \
--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;
as well as URLs for NNTP newsgroup(s).