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

Re: What's cooking in git.git (Oct 2009, #02; Sun, 11)

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 12, 2009, 22:52 UTC
Message-ID
<7vmy3w9qdd.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20091012051442.GB23007@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 27 quoted lines
> On Sun, Oct 11, 2009 at 08:18:17PM -0700, Junio C Hamano wrote:
>
>> * jk/1.7.0-status (2009-09-05) 5 commits.
>>  - docs: note that status configuration affects only long format
>>   (merged to 'next' on 2009-10-11 at 65c8513)
>>  + commit: support alternate status formats
>>  + status: add --porcelain output format
>>  + status: refactor format option parsing
>>  + status: refactor short-mode printing to its own function
>>  (this branch uses jc/1.7.0-status.)
>> 
>> Gives the --short output format to post 1.7.0 "git commit --dry-run" that
>> is similar to that of post 1.7.0 "git status".
>> 
>> * jc/1.7.0-status (2009-09-05) 4 commits.
>>   (merged to 'next' on 2009-10-11 at 9558627)
>>  + status: typo fix in usage
>>  + git status: not "commit --dry-run" anymore
>>  + git stat -s: short status output
>>  + git stat: the beginning of "status that is not a dry-run of commit"
>>  (this branch is used by jk/1.7.0-status.)
>> 
>> With this, "git status" is no longer "git commit --dry-run".
>
> Hmm. I thought you wanted to re-order some of these for to put the
> porcelain and short formats into v1.6.6, but leave the status switchover
> for v1.7.0.

We could build an alternate history between 3fa509d..46b77a6, revert the merges 9558627 and 65c8513, and merge the alternate history. But is the short format support so solid that it deserves to be in 1.6.6 in the current shape?

Previous: Jeff KingNext: Jeff King
Message 3 of 14 in “What's cooking in git.git (Oct 2009, #02; Sun, 11)”
  1. Junio C HamanoOct 12, 2009
  2. Jeff KingOct 12, 2009
  3. Junio C HamanoOct 12, 2009
  4. Jeff KingOct 14, 2009
  5. Sverre RabbelierOct 12, 2009
  6. Jens LehmannOct 14, 2009
  7. 1/4 Add the --submodule-summary option to the diff option familyJens Lehmann, Oct 14, 2009
  8. 2/4 fix indentation depth for git diff --submodule-summaryJens Lehmann, Oct 14, 2009
  9. 3/4 fix output for deleted submodules in git diff --submodule-summaryJens Lehmann, Oct 14, 2009
  10. 4/4 add tests for git diff --submodule-summaryJens Lehmann, Oct 14, 2009
  11. submodule-summaryJunio C Hamano, Oct 14, 2009
  12. Jens LehmannOct 14, 2009
  13. Junio C HamanoOct 14, 2009
  14. Jens LehmannOct 15, 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.