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

Re: What's cooking in git.git (Oct 2009, #01; Wed, 07)

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 9, 2009, 06:46 UTC
Message-ID
<7vk4z56p59.fsf@alter.siamese.dyndns.org>
In-Reply-To
<m3iqepgxcc.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
Show 12 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
>
>> --------------------------------------------------
>> [New Topics]
>
>> * jn/gitweb-patch (2009-09-30) 1 commit
>>  - gitweb: Do not show 'patch' link in 'commit' view for merges
>> 
>> jk: After some comments with Jakub, I think the code is right but he
>> promised a re-roll with more in the commit message.
>
> Not only better commit message, but a more complete patch as well.
Ok; I'll wait.
Show 8 quoted lines
>> * mr/gitweb-snapshot (2009-09-26) 2 commits
>>  - gitweb: append short hash ids to snapshot files
>>  - gitweb: check given hash before trying to create snapshot
>> 
>> jk: He posted a v5 of his series. I didn't look at it closely, but Jakub
>> ack'd it.
> ...
> In short: first patch is a go, second needs more work.

Ok; I'll merge fdb0c36 (gitweb: check given hash before trying to create snapshot, 2009-09-26) to 'next'.

Show 8 quoted lines
>> * jc/pretty-lf (2009-10-04) 1 commit
>>  - Pretty-format: %[+-]x to tweak inter-item newlines
>> 
>> I am not happy with this one yet.  I am contemplating to introduce a new
>> syntax "%[magic(param)<anything>%]" to generalize expressions of this and
>> line wrapping features in an extensible way.
>> ...
> So... it is magic %[...%] or %{...} or %{...%}?

The escape does not matter. %() is fine, too. It is non-essential for the purpose of the upcoming release so I have backburnered coming up with and thinking the details through.

Show 7 quoted lines
>> --------------------------------------------------
>> [Cooking]
>
>> * jn/gitweb-show-size (2009-09-07) 1 commit
>>  - gitweb: Add 'show-sizes' feature to show blob sizes in tree view
>
> What this one requires (beside better name for a feature)?
Name before 'next', and then the usual cooking, I guess.
Show 7 quoted lines
>> * jn/gitweb-blame (2009-09-01) 5 commits
>> ...
>> Ajax-y blame.
>
> I reordered patches so JSMIN one is first (as it is less
> controversial), but the 'create blame_incremental links' one needs
> more work.
Ok; I'll wait.
Thanks.
Previous: Jakub Narebski
Message 17 of 17 in “What's cooking in git.git (Oct 2009, #01; Wed, 07)”
  1. Junio C HamanoOct 8, 2009
  2. Johannes SchindelinOct 8, 2009
  3. Sverre RabbelierOct 8, 2009
  4. Shawn O. PearceOct 8, 2009
  5. Sverre RabbelierOct 8, 2009
  6. Matt McClureOct 11, 2009
  7. Sverre RabbelierOct 11, 2009
  8. Sverre RabbelierOct 28, 2009
  9. Ian ClatworthyOct 28, 2009
  10. Johannes SchindelinOct 29, 2009
  11. Ian ClatworthyOct 30, 2009
  12. Sverre RabbelierOct 30, 2009
  13. Marius Storm-OlsenOct 8, 2009
  14. Erik Faye-LundOct 8, 2009
  15. Junio C HamanoOct 9, 2009
  16. Jakub NarebskiOct 9, 2009
  17. Junio C HamanoOct 9, 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.