git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: svn versus git

From
Andreas Ericsson <ae@op5.se>
Date
Dec 15, 2006, 15:41 UTC
Message-ID
<4582C233.1000706@op5.se>
In-Reply-To
<200612151519.kBFFJSYn012227@laptop13.inf.utfsm.cl>
Horst H. von Brand wrote:
Show 36 quoted lines
> Jakub Narebski <jnareb@gmail.com> wrote:
>> Andy Parkins wrote:
>>
>>> On Wednesday 2006 December 13 22:56, Shawn Pearce wrote:
>>>
>>>>   git cat-file -p $REV:$file
>>>>
>>>> not sure how much easier it gets than that.  Load in the bash
>>>> completion from contrib/completion and you can even tab complete
>>>> the $file part.
>>> Yes.  I was a little unfair on that one; I forgot about the REV:file syntax.  
>>> However, it's still not simple for a new user; I think I'd say "draw" if 
>>> the "-p" weren't a requirement.
>>   $ git repo-config alias.less "-p cat-file -p"
>>   $ git repo-config alias.cat     "cat-file -p"
>>
>> remedies that.
>>
>> [...]
>>>> How is it unfriendly?  What specifically would you change to make
>>>> it more friendly?
>>> $ git-ls-tree v1.0.0
>>> 100644 blob 906e98492080d2fde9467a9970fc92d7a8cfeaf8    Makefile
> 
>>> I'm a newbie: what's that number at the front?  What's a blob?  What's
>>> that great big number - I've only seen commit hashes that look like
>>> that, and that isn't one.  Definitely not friendly.
> 
>> The number in front is octal mode of a file or directory. "blob"
>> is a file (or symbolic link), "tree" is a directory, all of this
>> can be found in git(7).
> 
> I don't want to come through as rude, but that you can find the explanation
> somewhere (and as an old(ish) Unix/git hand you know (or should be able to
> guess easily) what it means) doesn't help the _newbie_ confronted with this
> gibberish one iota.

I think it would help if we could write out things ls-style though and I'm all for axing the SHA1 (I don't even think the SHA1 of specific files of a tree can be *used* for anything), so the above would be

-rw-r--r-- Makefile

which most newbies should grok fairly quickly. Not least because it's familiar, and we can even toss in the size in that string without taking up too much screen real estate. If we try really hard to cater to people who have never seen ls output we're gonna end up annoying the other side of the camp so much that they'll walk away in disgust.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Previous: Horst H. von BrandNext: Junio C Hamano
Message 3 of 10 in “Re: git-show --stat on first commit”
  1. Horst H. von BrandNov 21, 2006
  2. Horst H. von BrandDec 15, 2006
  3. Andreas EricssonDec 15, 2006
  4. Junio C HamanoDec 15, 2006
  5. Horst H. von BrandDec 27, 2006
  6. Junio C HamanoDec 27, 2006
  7. Junio C HamanoDec 28, 2006
  8. Nicolas PitreDec 28, 2006
  9. David KågedalDec 29, 2006
  10. Horst H. von BrandJan 4, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.