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

Re: How to check repository/working tree status from a script

From
Johannes Sixt <j.sixt@viscovery.net>
Date
May 20, 2009, 11:32 UTC
Message-ID
<4A13EA4E.9050805@viscovery.net>
In-Reply-To
<20090520111028.GA15453@torres.zugschlus.de>
Marc Haber schrieb:
Show 12 quoted lines
> On Tue, May 19, 2009 at 09:18:12AM -0700, Linus Torvalds wrote:
>> And if what you want to know about is whether there are _new_ files you 
>> might want to check, then you need a third check: 'git ls-files'. You 
>> won't see it in the error code, but you can do
>>
>> 	others=$(git ls-files -o --exclude-standard)
>>
>> and then check it 'others' is empty or not.
> 
> So parsing the output is both the canonical and only way to do so
> since there is no meaningful exit code? Can I assume that the
> formatting of git output is not subject to change?
See 'man git':

"Porcelain" commands are *not* for use in scripts; their output may change. git diff, git status, git commit, git checkout are in this category.

"Plumbing" commands are for use in scripts and their output will not change. git ls-files, git diff-tree, git diff-files are in this category.

-- Hannes
Previous: Santi BéjarNext: Marc Haber
Message 11 of 15 in “How to check repository/working tree status from a script”
  1. Marc HaberMay 19, 2009
  2. Tony FinchMay 19, 2009
  3. Marc HaberMay 19, 2009
  4. Tony FinchMay 19, 2009
  5. Marc HaberMay 20, 2009
  6. Linus TorvaldsMay 19, 2009
  7. Linus TorvaldsMay 19, 2009
  8. Marc HaberMay 20, 2009
  9. Marc HaberMay 20, 2009
  10. Santi BéjarMay 20, 2009
  11. Johannes SixtMay 20, 2009
  12. Marc HaberMay 20, 2009
  13. Marc HaberMay 21, 2009
  14. Jeff KingMay 21, 2009
  15. Marc HaberMay 23, 2009

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.