From: Jonathan Nieder <jrnieder@gmail.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: cmd_struct
Date: Wed, 13 May 2015 16:23:49 -0700 [thread overview]
Message-ID: <20150513232348.GD5586@google.com> (raw)
In-Reply-To: <CACnwZYe5i3p0f7cvprya=VdhFnnMW_H=K18BFqjq_Qn86cjXeA@mail.gmail.com>
Hi,
Thiago Farina wrote:
> Would be too churn/noise (at this point) to rename cmd_struct to builtin_cmd?
>
> I know "Why" question could come, but I prefer to not answer it if I can.
The answer depends on the "why". (Not "why do you ask?", but "why
rename --- what benefit would it bring?")
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2015-05-13 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 23:10 cmd_struct Thiago Farina
2015-05-13 23:23 ` Jonathan Nieder [this message]
2015-05-13 23:24 ` cmd_struct Junio C Hamano
2015-05-13 23:31 ` cmd_struct Junio C Hamano
2015-05-14 7:49 ` cmd_struct Johannes Schindelin
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=20150513232348.GD5586@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=tfransosi@gmail.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