From: Jack Desert <jackdesert556@gmail.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: git@vger.kernel.org
Subject: Re: GIT counterpart to "svn list"
Date: Wed, 21 Apr 2010 22:37:16 -0500 [thread overview]
Message-ID: <20100421223716.6526f625@pennie-farthing> (raw)
In-Reply-To: <4BCFC180.5020009@dbservice.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
El Thu, 22 Apr 2010 05:24:48 +0200
Tomas Carnecky <tom@dbservice.com> escribió:
> On 4/22/10 5:22 AM, Jack Desert wrote:
> >
> > I'm new to GIT, and the one command I can't live without is:
> > svn list
> > Is ther a GIT couterpart to svn list?
>
> We're all clueless about how svn works, or what svn list does. Can you
> enlighten us please?
>
> tom
>
"svn list" displays which files and folders in the current directory are under version control. It's helpful in figuring out which files you still need to add to the repository. Attached is sample output from one of my directories under subversion souce control.
-Jack
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jack Desert -- Writer, Entrepeneur
Author and Spokesman: www.LetsEATalready.com
Software Developer: http://GrooveTask.org
Email: JackDesert556@gmail.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[-- Attachment #2: svn_list_demo --]
[-- Type: application/octet-stream, Size: 100 bytes --]
Blog/
LyxBlog/
README.build
__init__.py
coalesce.py
io/
seed.py
test_coalesce.py
test_seed.py
util/
next prev parent reply other threads:[~2010-04-22 3:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 3:22 GIT counterpart to "svn list" Jack Desert
2010-04-22 3:24 ` Tomas Carnecky
2010-04-22 3:37 ` Jack Desert [this message]
2010-04-22 3:45 ` Alexander Iljin
2010-04-22 3:47 ` Tomas Carnecky
2010-04-22 7:41 ` Michael J Gruber
2010-04-22 10:44 ` Alex Riesen
2010-04-22 8:56 ` Santi Béjar
2010-04-22 11:51 ` Git - SVN Crash Course Petr Baudis
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=20100421223716.6526f625@pennie-farthing \
--to=jackdesert556@gmail.com \
--cc=git@vger.kernel.org \
--cc=tom@dbservice.com \
/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).