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

Re: Salvaging borked project history

From
MMason <slash.tmp@free.fr>
Date
Feb 26, 2015, 23:47 UTC
Message-ID
<54EFB0AE.6000600@free.fr>
In-Reply-To
<xmqqioeol5v4.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
Show 6 quoted lines
> Mason wrote:
> 
>> I was planning to write 'git diff -q commit^ commit'
>> to test for empty commits.
> 
> s/-q/--quiet/ and all is well, no?
Doh! I've no idea how I missed these...
--exit-code
  Make the program exit with codes similar to diff(1). That is, it
  exits with 1 if there were differences and 0 means no differences.
--quiet
  Disable all output of the program. Implies --exit-code.
Thanks for walking me through it.
Regards.
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 9 in “Salvaging borked project history”
  1. MasonFeb 23, 2015
  2. Junio C HamanoFeb 23, 2015
  3. MasonFeb 26, 2015
  4. Junio C HamanoFeb 26, 2015
  5. MasonFeb 26, 2015
  6. Junio C HamanoFeb 26, 2015
  7. MasonFeb 26, 2015
  8. Junio C HamanoFeb 26, 2015
  9. MasonMar 4, 2015

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.