git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
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 18:25:12 -0400	[thread overview]
Message-ID: <20050813222512.GA6844@mythryan2.michonline.com> (raw)
In-Reply-To: <7v64uaqknh.fsf@assigned-by-dhcp.cox.net>

On Sat, Aug 13, 2005 at 01:57:22AM -0700, Junio C Hamano wrote:
> 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?

Well, I was really responding to the comment about "-script" being
better than ".sh", as trying ".sh", ".pl", ".php", etc, would rapidly
be annoying.

Honestly, I think the biggest argument against the "-script" suffix is
related to man-page usage:  It requires significant knowledge of the Git
project to figure out what name variant to use to find the man page.

(There are other problems with man pages, but I'll address those
seperately now that they have occurred to me.)

-- 

Ryan Anderson
  sometimes Pug Majere

  parent reply	other threads:[~2005-08-13 22:25 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
2005-08-13 16:35         ` Linus Torvalds
2005-08-13 22:25         ` Ryan Anderson [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050813222512.GA6844@mythryan2.michonline.com \
    --to=ryan@michonline.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).