From: Jonathan Nieder <jrnieder@gmail.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] help.c: Pull cmd_version out of this file.
Date: Wed, 1 Sep 2010 23:35:00 -0500 [thread overview]
Message-ID: <20100902043500.GF29713@burratino> (raw)
In-Reply-To: <AANLkTinHJHzcoFFjv-TaQ+DYVyqn46fqA802m8Lq5anp@mail.gmail.com>
Thiago Farina wrote:
> All patches should just fix real problems?
Yes.
> I think it just makes more sense, since *all* other commands are in
> builtin/ and it's own files.
I was careless before and was not even thinking about
BUILT_INS += $(patsubst builtin/%.o,git-%$X,$(BUILTIN_OBJS))
Sorry.
With that line in mind, what Junio wrote in the "what's cooking"
message makes a lot of sense. A good direction to go in long term
might be to freeze the list of built-ins installed to $gitexecdir in
some clean way and avoid adding new ones.
Would you be interested in working on that? That would solve a
problem (turning back the tide of scripts that use git- commands,
without breaking compatibility) that some people are interested in.
The hardest part would probably be to make sure commands like
"git help version" work properly.
next prev parent reply other threads:[~2010-09-02 4:36 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
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 [this message]
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=20100902043500.GF29713@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).