From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: [kernel.org users] README and ChangeLog files
Date: Thu, 21 Aug 2008 18:32:36 +0200 [thread overview]
Message-ID: <g8k5b6$32a$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808210830080.3487@nehalem.linux-foundation.org>
Linus Torvalds venit, vidit, dixit 21.08.2008 17:35:
>
> On Wed, 20 Aug 2008, H. Peter Anvin wrote:
>> Personally, I think this grand renaming was a huge step backwards; an attempt
>> to be bug-compatible with other SCMs. The only people I personally ever saw
>> complaining about the situation in the first place were people who were
>> fanbois of some other SCM.
>
> Heh. It's true that the push came from people who were used to the "scm
> xyz" model, but it's also true that git basically made the situation in
> /usb/bin even worse.
>
> You _can_ actually have the "best of both worlds" (if you really do want
> to continue the "git-xyzzy" usage) by doing
>
> PATH=$PATH:$(git --exec-path)
>
> although there has been noise about removing the built-in commands
> entirely even from there. I'm cc'ing the git mailing list just to bring
> the point up - I'm the one who actually championed removing the
> "unnecessary" hardlinks, and it seems that nto doing so was the right
> choice.
>
> One of the reasons that the dashed format is being removed is a real
> technical one, though: git aliases. They never supported the dashed
> format, since they never were real executables (that's the whole point of
> an alias, after all).
>
> So even with the above path thing, you'll still have to use the spacey
> version for any aliases you use.
Come to think of it: Maybe commands like "git pull" should, when
spitting out warnings, refer to "git help pull" rather than
"git-pull(1)" now. I do like it spacey, but the man issue is confusing.
It continues with the links in the help/man pages, of course.
Michael
next prev parent reply other threads:[~2008-08-21 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48AC5972.80908@zytor.com>
[not found] ` <20080820182636.GJ8318@parisc-linux.org>
[not found] ` <48AC6839.7050605@zytor.com>
[not found] ` <1219264114.7576.1121.camel@calx>
[not found] ` <20080820210733.GA418@smurf.noris.de>
[not found] ` <20080820223033.GD18947@flint.arm.linux.org.uk>
[not found] ` <alpine.LFD.1.10.0808201552070.3487@nehalem.linux-foundation.org>
[not found] ` <57C9024A16AD2D4C97DC78E552063EA309E70713@orsmsx505.amr.corp.intel.com>
[not found] ` <20080820232332.GE18947@flint.arm.linux.org.uk>
[not found] ` <alpine.LFD.1.10.0808201629590.3487@nehalem.linux-foundation.org>
[not found] ` <m163pv59lo.fsf@frodo.ebiederm.org>
[not found] ` <48AD03BD.9000909@zytor.com>
2008-08-21 15:35 ` [kernel.org users] README and ChangeLog files Linus Torvalds
2008-08-21 16:01 ` Petr Baudis
2008-08-21 16:32 ` Michael J Gruber [this message]
[not found] ` <1219273792.7576.1146.camel@calx>
[not found] ` <alpine.LFD.1.10.0808201622260.3487@nehalem.linux-foundation.org>
[not found] ` <1219294266.7576.1180.camel@calx>
[not found] ` <20080821125945.GE16634@mit.edu>
[not found] ` <7vk5eaez0m.fsf@gitster.siamese.dyndns.org>
[not found] ` <20080822082908.GA29475@isilmar.linta.de>
2008-08-22 21:13 ` Junio C Hamano
2008-08-22 23:09 ` Jeff Garzik
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='g8k5b6$32a$1@ger.gmane.org' \
--to=michaeljgruber+gmane@fastmail.fm \
--cc=git@vger.kernel.org \
/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).