From: Junio C Hamano <junkio@cox•net>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: git@vger•kernel.org, Nguyen Thai Ngoc Duy <pclouds@gmail•com>
Subject: Re: svn versus git
Date: Fri, 15 Dec 2006 13:55:11 -0800 [thread overview]
Message-ID: <7v64ccomdc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0612152117390.3635@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
> Hi,
>
> On Fri, 15 Dec 2006, Johannes Schindelin wrote:
>
>> On Fri, 15 Dec 2006, Nguyen Thai Ngoc Duy wrote:
>>
>> > About adding index support to git-show, yes it's really messy. index
>> > doesn't have tree objects.
>>
>> Insofar, it is not messy: git-show only shows _objects_. For example, "git
>> show :README" works as expected if you have a file called "README" in the
>> index...
>
> Note: this is not completely true. The index contains cache_trees...
Let's not go there.
I was reviewing the list of plumbing in Documentation/git.txt
last night, and I think ls-files is the only command that user
may still want to use from the command line every day.
I originally thought that it would only be after a conflicted
merge, always with -u option, but some people seem to find that
"ls-files --others" and friends are useful (I never use that
myself) and if so what it does really in the realm of Porcelain.
I haven't formed a firm opinion on this yet, but possibilities
are:
* we reclassify ls-files as a Porcelain-ish (but do not change
its UI nor defaults at all); we might want to give a shorter
alias to the command, though, if we go this route.
* we give '--list' option to 'git show' and in such a case,
lack of objects does not default to HEAD -- when no object is
given it internally diverts to cmd_ls_files() instead;
* we add 'git ls' command to give Porcelain-ish access to
ls-tree and ls-files.
next prev parent reply other threads:[~2006-12-15 21:56 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 22:00 svn versus git Andy Parkins
2006-12-13 22:18 ` J. Bruce Fields
2006-12-13 23:20 ` [PATCH] Document the simple way of using of git-cat-file Robin Rosenberg
2006-12-13 23:55 ` Jakub Narebski
2006-12-14 0:29 ` Johannes Schindelin
2006-12-14 0:35 ` Jakub Narebski
2006-12-13 22:29 ` svn versus git Jakub Narebski
2006-12-13 22:51 ` Andy Parkins
2006-12-13 23:14 ` Jakub Narebski
2006-12-13 23:17 ` Shawn Pearce
2006-12-13 23:32 ` Peter Baumann
2006-12-13 22:56 ` Shawn Pearce
2006-12-13 23:17 ` Jakub Narebski
2006-12-13 23:26 ` Shawn Pearce
2006-12-14 9:08 ` Andy Parkins
2006-12-14 9:44 ` Junio C Hamano
2006-12-14 10:42 ` Andy Parkins
2006-12-14 15:08 ` Nguyen Thai Ngoc Duy
2006-12-14 15:31 ` Johannes Schindelin
2006-12-14 16:32 ` Nguyen Thai Ngoc Duy
2006-12-14 16:55 ` Johannes Schindelin
2006-12-14 17:10 ` Nguyen Thai Ngoc Duy
2006-12-15 0:19 ` Johannes Schindelin
2006-12-15 15:26 ` Nguyen Thai Ngoc Duy
2006-12-15 20:15 ` Johannes Schindelin
2006-12-15 20:19 ` Johannes Schindelin
2006-12-15 21:55 ` Junio C Hamano [this message]
2006-12-15 22:37 ` Nicolas Pitre
2006-12-16 0:26 ` Nguyen Thai Ngoc Duy
2006-12-15 11:27 ` Jakub Narebski
2006-12-15 12:08 ` Andy Parkins
2006-12-15 15:19 ` Horst H. von Brand
2006-12-15 15:41 ` Andreas Ericsson
2006-12-15 18:14 ` Junio C Hamano
2006-12-14 15:55 ` Seth Falcon
2006-12-15 11:35 ` Jakub Narebski
2006-12-13 23:24 ` Robin Rosenberg
2006-12-13 23:45 ` Junio C Hamano
2006-12-14 9:19 ` Andy Parkins
2006-12-14 19:00 ` Arkadiusz Miskiewicz
2006-12-14 22:07 ` Andreas Ericsson
2006-12-14 22:13 ` Arkadiusz Miskiewicz
2006-12-14 22:23 ` Shawn Pearce
2006-12-15 8:52 ` Andreas Ericsson
2006-12-14 23:10 ` Johannes Schindelin
2006-12-15 12:56 ` Jakub Narebski
2006-12-15 0:58 ` Horst H. von Brand
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=7v64ccomdc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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