All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2010, #03; Wed, 07)
Date: Thu, 8 Apr 2010 03:38:26 -0400	[thread overview]
Message-ID: <20100408073825.GA15153@coredump.intra.peff.net> (raw)
In-Reply-To: <7v6342ahx9.fsf@alter.siamese.dyndns.org>

On Wed, Apr 07, 2010 at 05:48:02PM -0700, Junio C Hamano wrote:

> * jc/test-sleepless (2010-04-06) 1 commit
>   (merged to 'next' on 2010-04-07 at 8ccf40a)
>  + war on "sleep" in tests

I read this one, and it looked fine to me.

> * sd/log-decorate (2010-04-06) 4 commits
>   (merged to 'next' on 2010-04-06 at 992c9ad)
>  + log --pretty/--oneline: ignore log.decorate
>   (merged to 'next' on 2010-03-08 at 58a6fba)
>  + log.decorate: usability fixes
>  + Add `log.decorate' configuration variable.
>  + git_config_maybe_bool()
> 
> I did the tip one myself.  An extra set or two of eyeballs would be
> appreciated.

I just responded in that thread.

> * jk/cached-textconv (2010-04-01) 7 commits
>   (merged to 'next' on 2010-04-02 at a023e3c)
>  + diff: avoid useless filespec population
>  + diff: cache textconv output
>  + textconv: refactor calls to run_textconv
>  + introduce notes-cache interface
>  + make commit_tree a library function
>  + fix textconv leak in emit_rewrite_diff
>  + fix const-correctness of write_sha1_file

You mentioned pushing this off to 1.7.2. I don't have a problem with
that, but you may want to cherry-pick or merge up to the "fix textconv
leak", as it is an unrelated fix.

I think it makes sense to target 1.7.2 with the feature, and then flip
the default for diff.*.cachetextconv to 'true' in 1.7.3. That will give
it some wider exposure before we start running it by default.

> * nd/setup (2010-04-05) 43 commits
> [...]
> Rerolled.  I need to look at this series during the feature freeze so that
> we can decide to (or not to) include it in 'next' early in post 1.7.1 cycle.

I really should review this, but it's just so dauntingly large and
boring looking that I haven't gotten around to it. Probably one or both
of us should look at it before applying it to next, but assuming it
passes a basic sanity check, I think the best thing will be to get it in
'next' early so we can shake out any bugs during the next cycle.

-Peff

  parent reply	other threads:[~2010-04-08  7:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  0:48 What's cooking in git.git (Apr 2010, #03; Wed, 07) Junio C Hamano
2010-04-08  6:05 ` Johannes Sixt
2010-04-08  6:33   ` Junio C Hamano
2010-04-08  9:01     ` Fredrik Kuivinen
2010-04-08  9:14       ` ***SPAM*** " Tor Arntsen
2010-04-08  9:16         ` Tor Arntsen
2010-04-08  7:38 ` Jeff King [this message]
2010-04-08 21:42   ` nd/setup Jonathan Nieder
2010-04-09  0:13     ` nd/setup Jeff King
2010-04-11 11:01       ` [PATCH] Take it easy on unallowed access to non-existent repository Nguyễn Thái Ngọc Duy
2010-04-11 15:45         ` Sverre Rabbelier
2010-04-11 17:49           ` Nguyen Thai Ngoc Duy
2010-04-11 17:52             ` Sverre Rabbelier
2010-04-11 17:57               ` Nguyen Thai Ngoc Duy
2010-04-09  5:46     ` nd/setup Nguyen Thai Ngoc Duy
2010-04-09  5:57       ` nd/setup Jonathan Nieder
2010-04-09  6:56         ` nd/setup Nguyen Thai Ngoc Duy
2010-04-11 17:57     ` nd/setup Nguyen Thai Ngoc Duy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100408073825.GA15153@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.