git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: svn versus git
Date: Thu, 14 Dec 2006 10:42:08 +0000	[thread overview]
Message-ID: <200612141042.09453.andyparkins@gmail.com> (raw)
In-Reply-To: <7vodq695ha.fsf@assigned-by-dhcp.cox.net>

On Thursday 2006 December 14 09:44, Junio C Hamano wrote:

> I would say pretending as if cat-file is a Porcelain is the
> unfair part.

I had to; there is no other equivalent of "svn cat" in git.

> Again, mistaking ls-tree as if it was a Porcelain is the true
> cause of the newbie confusion.

Again, there is no other equivalent of "svn list" in git.

> If a Porcelain level "ls" is needed (and I am doubtful about
> usefulness of "svn list -r538" like command), that is the

Me too.  I was in no way advocating that git should try to be SVN (shudder).  
As I was comparing though, I had to pick git commands that did at least what 
SVN could do.

> command you would want to teach about using ls-files and ls-tree
> depending on what the end users want in their workflow.

Personally, I think qgit fills an awfully big hole in svn that makes them all 
irrelevant.  qgit is a much better repository browsing tool than "svn list" 
is.



Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE

  reply	other threads:[~2006-12-14 10:42 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 [this message]
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
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=200612141042.09453.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --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).