git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2013, #03; Thu, 6)
Date: Fri, 7 Jun 2013 22:06:57 +0200	[thread overview]
Message-ID: <20130607200657.GC31625@goldbirke> (raw)
In-Reply-To: <CALkWK0mkQqopPBrmO1e20nN_kbNLgcR4cA9z7nOfA4q_2GxvMg@mail.gmail.com>

On Sat, Jun 08, 2013 at 01:17:28AM +0530, Ramkumar Ramachandra wrote:
> SZEDER Gábor wrote:
> > because nowadays __git_complete_file() is a wrapper around
> > __git_complete_revlist_file().
> 
> What?  It was never anything different from a poorly-named alias for
> __git_complete_revlist_file().

Again: __git_complete_file() has been there since the completion
script was first included in git.

>  You have already agreed that
> __git_complete_file() is a horrible name, so why not deprecate it?

I am not against deprecating it, and by "it" I mean the function name.

> Whom is this confusion benefiting, and how is it any "cleaner"?

It's clearer because of the reasons I gave in my other email in the
discussion of the patch.

Plus it would avoid commits on master with incorrect commit messages.

> If
> you're arguing about expanding __git_complete_file(), don't do that:
> just write a new function and give it a proper name.

I am not arguing about that.

  reply	other threads:[~2013-06-07 20:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 22:41 What's cooking in git.git (Jun 2013, #03; Thu, 6) Junio C Hamano
2013-06-07  0:00 ` SZEDER Gábor
2013-06-07  1:05   ` Junio C Hamano
2013-06-07 15:57     ` Junio C Hamano
2013-06-07 19:34     ` SZEDER Gábor
2013-06-07 19:47       ` Ramkumar Ramachandra
2013-06-07 20:06         ` SZEDER Gábor [this message]
2013-06-07 17:30   ` Ramkumar Ramachandra
2013-06-07 18:41     ` Junio C Hamano
2013-06-07 19:01       ` Ramkumar Ramachandra
2013-06-07 19:16       ` SZEDER Gábor
2013-06-07 19:46         ` Junio C Hamano
2013-06-07 20:44           ` SZEDER Gábor
2013-06-07 21:53             ` Junio C Hamano
2013-06-08  0:11               ` SZEDER Gábor
2013-06-09 21:20                 ` Junio C Hamano
2013-06-09 21:48                   ` SZEDER Gábor
2013-06-09 22:56                     ` Junio C Hamano
2013-06-10  6:25                   ` Ramkumar Ramachandra
2013-06-10  7:00                     ` Junio C Hamano
2013-06-10  7:41                       ` Ramkumar Ramachandra
2013-06-07 18:55     ` SZEDER Gábor
2013-06-08 15:30 ` Ramkumar Ramachandra
2013-06-08 18:39   ` Matthieu Moy

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=20130607200657.GC31625@goldbirke \
    --to=szeder@ira.uka.de \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).