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

Re: 'git commit --short' without touching index?

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 5, 2010, 20:10 UTC
Message-ID
<7veifhy9j0.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100703091748.GA11714@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> It would be nice if the index-refreshing code only wrote to the index if
> there was something worth writing. I'm not sure how hard that would be
> to implement, though.
Hmm, don't we already do that with "istate->cache_changed"?

In any case, we should diagnose "commit --short" (and "--procelain") as an error, perhaps by splitting option parsers for commit and status further.

Previous: friedan@muon.rutgers.eduNext: Jeff King
Message 4 of 7 in “'git commit --short' without touching index?”
  1. DanielJul 3, 2010
  2. Jeff KingJul 3, 2010
  3. friedan@muon.rutgers.eduJul 3, 2010
  4. Junio C HamanoJul 5, 2010
  5. Jeff KingJul 5, 2010
  6. Junio C HamanoJul 5, 2010
  7. Jeff KingJul 6, 2010

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.