Re: Tool renames? was Re: First stab at glossary

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Sep 3, 2005, 06:54 UTC
Message-ID: <Pine.LNX.4.63.0509030233350.23242@iabervon.org>
In-Reply-To: <7v8xyebs9v.fsf@assigned-by-dhcp.cox.net>

On Fri, 2 Sep 2005, Junio C Hamano wrote:

Show 13 quoted lines

> I said:
> 
> > 	I'll draw up a strawman tonight unless somebody else
> > 	does it first.
> 
> 1. Say 'index' when you are tempted to say 'cache'.
> 
>         git-checkout-cache      git-checkout-index
>         git-convert-cache       git-convert-index
>         git-diff-cache          git-diff-index
>         git-fsck-cache          git-fsck-index
>         git-merge-cache         git-merge-index
>         git-update-cache        git-update-index

Agreed, except that git-convert-cache and git-fsck-cache actually have nothing to do this the index by any name, and should probably be git-convert-objects and git-fsck-objects.

Show 11 quoted lines

> 2. The act of combining two or more heads is called 'merging';
>    fetching immediately followed by merging is called 'pulling'.
> 
>         git-resolve-script      git-merge-script
> 
>    The commit walkers are called *-pull, but this is probably
>    confusing.  They are not pulling.
> 
>         git-http-pull           git-http-walk
>         git-local-pull          git-local-walk
>         git-ssh-pull            git-ssh-walk

I think "fetch" is more applicable to what they do.

Show 12 quoted lines

> 3. Non-binaries are called '*-scripts'.
> 
>    In earlier discussions some people seem to like the
>    distinction between *-script and others; I did not
>    particularly like it, but I am throwing this in for
>    discussion.
> 
>         git-applymbox           git-applymbox-script
>         git-applypatch          git-applypatch-script
>         git-cherry              git-cherry-script
>         git-shortlog            git-shortlog-script
>         git-whatchanged         git-whatchanged-script

I don't think it matters very much whether something is a script or not; on the other hand, it would be good to have "git" list a reasonable set of commands to use through the interface, which would exclude, for example, git-merge-one-file-script, and include the above commands.

> 4. To be removed shortly.
> 
>         git-clone-dumb-http     should be folded into git-clone-script

Agreed.

	-Daniel
*This .sig left intentionally blank*