Thank you William.
On Sunday, December 9, 2012 1:50:45 AM UTC+1, William Mizuta wrote:
>
> If you know the directory hash code, you can use git ls-tree hash. To know
> your directory hash you can use git ls-tree HEAD, which shows you every
> file/directory hash of your project root.
> [...]
>
-
Thank you Ryan, that is what I was looking for.
--
If you know the directory hash code, you can use git ls-tree hash. To know
your directory hash you can use git ls-tree HEAD, which shows you every
file/directory hash of your project root.
William Seiti Mizuta
@williammizuta
Desenvolvedor da Caelum
On Sat, Dec 8, 2012 at 7:07 PM, Ryan Hodson
Try git ls-files (no hyphen after the git command).
On Dec 8, 2012 3:00 PM, "Fanta" wrote:
>
> Thank you Ryan. git status only lists files the are untracked (and not
listed in .gitignore) or to be committed.
>
> --
>
>
--
Thank you Ryan. git status only lists files the are untracked (and not
listed in .gitignore) or to be committed.
--
Thank you; I guess the command works under Unix. Under Windows it doesn't:
*C:\workspace>git ls files
git: 'ls' is not a git command. See 'git --help'.
Did you mean this?
log
C:\workspace>git-ls-files
'git-ls-files' is not recognized as an internal or external command,
operable program o
git status would also do the trick.
On Dec 8, 2012 10:55 AM, "Philip Oakley" wrote:
> **
> git-ls-files - Show information about files in the index and the working
> tree
>
> (--[cached|deleted|others|ignored|stage|unmerged|killed|modified])*
>
> - Original Message -
> *From:* Fanta
> *T
git-ls-files - Show information about files in the index and the working tree
(--[cached|deleted|others|ignored|stage|unmerged|killed|modified])*
- Original Message -
From: Fanta
To: git-users@googlegroups.com
Sent: Saturday, December 08, 2012 4:03 PM
Subject: [git-users] How
