From: Junio C Hamano <gitster@pobox.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] help.c: Pull cmd_version out of this file.
Date: Tue, 31 Aug 2010 23:11:21 -0700 [thread overview]
Message-ID: <7v1v9e803a.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTimDjRz=JmiVn+ybQ5ewaj=7N5tp48fUArD5vG_H@mail.gmail.com> (Thiago Farina's message of "Tue\, 31 Aug 2010 23\:38\:57 -0300")
Thiago Farina <tfransosi@gmail.com> writes:
> On Sun, Aug 29, 2010 at 11:40 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Jonathan Nieder wrote:
>>> Thiago Farina wrote:
>>>
>>>> Promote cmd_version to a builtin, by moving it to its own file
>>>> in builtin/version.c
>> [...]
>> So for what it's worth,
>>
>> Acked-by: Jonathan Nieder <jrnieder@gmail.com>
>
> Ping Junio.
If the patch were to also move git_version_string[] from git.c to this new
file, whose sole purpose will be to give the version information, then it
might be worth it, as we would need to recompile a file with only 10 lines
instead of git.c with 570 lines, but what the patch does is not even that.
Not that I would be happy to see such a change that affects dependency and
risk causing broken builds this late in the cycle, though.
I ended up spending 10+ minutes re-checking how the dependency between the
version string and the resulting binaries work. The patch probably would
cause "git clean" to report a new unignored file, too.
What did we gain through this exercise? Did we fix any real problem?
"git grep" sees directory boundaries through just fine, and I do not find
Jonathan's explanation very satisfactory.
Junio, who gets a lot more grumpy than necessary at night...
next prev parent reply other threads:[~2010-09-01 6:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 20:44 [PATCH] help.c: Pull cmd_version out of this file Thiago Farina
2010-08-30 2:38 ` Jonathan Nieder
2010-08-30 2:40 ` Jonathan Nieder
2010-09-01 2:38 ` Thiago Farina
2010-09-01 3:04 ` Nguyen Thai Ngoc Duy
2010-09-01 3:11 ` Thiago Farina
2010-09-01 6:11 ` Junio C Hamano [this message]
2010-09-01 6:22 ` Thiago Farina
2010-09-02 1:04 ` Junio C Hamano
2010-09-02 1:16 ` Thiago Farina
2010-09-02 4:35 ` Jonathan Nieder
2010-09-02 16:31 ` Junio C Hamano
2010-10-27 15:12 ` Thiago Farina
2010-10-27 15:18 ` Jonathan Nieder
2010-10-27 16:06 ` Thiago Farina
2010-10-27 16:45 ` Jonathan Nieder
2010-10-28 2:13 ` Thiago Farina
2010-10-28 3:11 ` Jonathan Nieder
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=7v1v9e803a.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).