git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 6/6] t9400, t9401: use "git cvsserver" without dash
Date: Tue, 09 Sep 2008 14:38:31 -0700	[thread overview]
Message-ID: <7vljy13sq0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080910062529.6117@nanako3.lavabit.com

Nanako Shiraishi <nanako3@lavabit.com> writes:

> The environment variable CVS_SERVER is still set to "git-cvsserver",
> because tests fail with CVS_SERVER='git cvsserver' (or double quotes).

My eyes are getting dry after looking at these s/git-/git / patches, so
please do not get offended if I leave these in my Inbox unread for a few
days.

But I think this particular one is worth mentioning something about, so I
am responding to it now.

To me, the above suggests that:

 * we should install git-cvsserver in $(bindir) so that it can be found on
   $PATH; and

 * it would be better to encourage users to consistently use
   "git-cvsserver" everywhere instead of "git cvsserver"; hence

 * this [6/6] in the series should be discarded.

We already install "server side programs" in $(bindir).

When we think about any of these server side programs, we do not think of
it as a feature chosen by the subcommand word on the command line given to
a program "git" (even though for built-ins, internal implementation might
allow such usage).

Instead we think of it as a single freestanding program in git suite.  For
example, when people talk about "You can use git-shell as your user's
login shell to limit the potential damage to your system", they do not
mean "the shell subcommand of git", but they mean the git-shell "program".

We do not run "git in daemon mode", but run "git-daemon" which is the
daemon program that serves native git protocol.

So why don't we do this (not just for test but for documentation as well)?

 * We do not use "git foo" form when refering to the "server side
   programs".  Make it official;

 * We move "server side programs" in git(7) documentation into its
   separate subsection; and

 * We always install "server side programs" in $(bindir).

I think git-cvsserver is the last one we missed from the set of server
side programs (git-cvsserver, git-daemon, git-receive-pack,
git-upload-archive, git-upload-pack).

  reply	other threads:[~2008-09-09 21:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 21:25 [PATCH 6/6] t9400, t9401: use "git cvsserver" without dash Nanako Shiraishi
2008-09-09 21:38 ` Junio C Hamano [this message]
2008-09-09 21:56   ` Jeff King
2008-09-10  4:13     ` Junio C Hamano
2008-09-10 11:03 ` Nanako Shiraishi
2008-09-10 22:37   ` Junio C Hamano
2008-10-28 11:16     ` Dmitry V. Levin
2008-10-28 15:57       ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09 21:50 Nanako Shiraishi

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=7vljy13sq0.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nanako3@lavabit.com \
    /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).