On Aug 28, 2008, at 9:35 AM, Linus Torvalds wrote:
On Thu, 28 Aug 2008, Perry Wagle wrote:
The PATH thing fixes the problem of typing in git-commands at the
command line, but not for scripts containing git<DASH> commands.
I've
seen no-one rebut my rebuttal.
What drugs are you people on?
No drugs, just that I was expecting people to do more than demonstrate
to me the excellence of their knee reflex. Especially you (Linus),
who supports thinking things out and not depending on debugging tools.
I prefer to think things out and not "coding from the hip". I can be
proven wrong, but you are going to have to engage your brain to do
so. Threatening me or whacking me with the neural loop from your
spine to your knee isn't going to cut it.
Just put it in your .bash_profile or something. It will now work for
all
your scripts.
In terms of continuing to provide me git<DASH><TAB> if I so desire,
that's an excellent idea, and I've repeatedly said so.
In terms of preserving scripts, thats a filthy hack that only fixes my
own execution of those scripts, not for other people. And some people
don't run bash, so /etc/bashrc *on every system* or whatever doesn't
actually do it either. Did you think that out?
And for us people who do _not_ want it, we fix the scripts, or we
don't
run them.
This is one upward compatibility broken for goofy reasons, at least
those given in this thread, where there were numerous "ZOMG! I get
143 completions!" accompanied by false claims that it was a 143
element *list* when in fact a *hash table* is used.
But the issue for me is what other upward compatibilities were
broken? What am I testing for? Is is really only that I
sed s/git-/git<SPACE>/g
on the scripts? I'm doubting it, given the quality of reasoning and
lack of respect for upward compatibility on this thread.
Yes, I'm over-killing a molehill, but I see you all building a
mountain in the distance that I don't feel like climbing. I haven't
been paid to do git stuff for months.
-- Perry
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
