All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Buchacher <drizzd@aon.at>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, dfowler <davidfowl@gmail.com>,
	git@vger.kernel.org, msysgit@googlegroups.com,
	Paul Betts <paul@github.com>, David Ebbo <david.ebbo@gmail.com>
Subject: Re: 1.7.10 doesn't show file pushstatus
Date: Tue, 1 May 2012 11:32:30 +0200	[thread overview]
Message-ID: <20120501093230.GA22633@ecki.lan> (raw)
In-Reply-To: <20120501084048.GA21904@sigill.intra.peff.net>

On Tue, May 01, 2012 at 04:40:49AM -0400, Jeff King wrote:
> 
> The following patch series fixes this:
> 
>   [1/3]: send-pack: show progress when isatty(2)
>   [2/3]: teach send-pack about --[no-]progress
>   [3/3]: t5541: test more combinations of --progress

Thanks. Looks good to me, although I completely missed this before. But
the tests should hopefully take care of any future regressions.

  parent reply	other threads:[~2012-05-01  9:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120501010609.GA14715@jupiter.local>
2012-05-01  6:58 ` 1.7.10 doesn't show file pushstatus Jeff King
2012-05-01  7:33   ` Jeff King
2012-05-01  8:40     ` Jeff King
2012-05-01  8:41       ` [PATCH 1/3] send-pack: show progress when isatty(2) Jeff King
2012-05-01  8:42       ` [PATCH 2/3] teach send-pack about --[no-]progress Jeff King
2012-05-01  8:43       ` [PATCH 3/3] t5541: test more combinations of --progress Jeff King
2012-05-01  9:35         ` Clemens Buchacher
2012-05-01  9:37           ` Jeff King
2012-05-01 17:53             ` David Ebbo
2012-05-01 20:45         ` Zbigniew Jędrzejewski-Szmek
2012-05-01 20:53           ` Junio C Hamano
2012-05-01  9:32       ` Clemens Buchacher [this message]
2012-05-01 17:33         ` 1.7.10 doesn't show file pushstatus Junio C Hamano
2012-05-02  1:04       ` Johannes Schindelin

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=20120501093230.GA22633@ecki.lan \
    --to=drizzd@aon.at \
    --cc=david.ebbo@gmail.com \
    --cc=davidfowl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=msysgit@googlegroups.com \
    --cc=paul@github.com \
    --cc=peff@peff.net \
    /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.