Git development
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: verify_pack.c vs verify-pack.c
Date: Thu, 30 Jun 2005 16:35:45 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0506301631480.1667@localhost.localdomain> (raw)
In-Reply-To: <7vy88r1tcp.fsf@assigned-by-dhcp.cox.net>

On Thu, 30 Jun 2005, Junio C Hamano wrote:

> >>>>> "NP" == Nicolas Pitre <nico@cam.org> writes:
> 
> NP> This is confusing.  Isn't possible to rename git-verify-pack to, say, 
> NP> git-fsck-pack instead?
> 
> Yes it is possible (I am not attached to the name).  The
> question is what to name it.

... or you could rename verify_pack.c to pack-check.c or whatever.

> BTW, is there a filesystem that would house the source to the
> core GIT that do not like names that differ only in underscore
> and dash?

Probably not.  It is just weird in a ls output that's all.  Certainly 
not a big issue.


Nicolas

  reply	other threads:[~2005-06-30 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 17:41 verify_pack.c vs verify-pack.c Nicolas Pitre
2005-06-30 20:29 ` Junio C Hamano
2005-06-30 20:35   ` Nicolas Pitre [this message]
2005-07-01  2:01     ` Jon Seymour

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=Pine.LNX.4.63.0506301631480.1667@localhost.localdomain \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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