From: James Cloos <cloos@jhcloos.com>
To: git@vger.kernel.org
Subject: [PATCH 0/1] Improve progress display in kB range.
Date: Sun, 19 Apr 2009 00:38:53 -0400 [thread overview]
Message-ID: <cover.1240115957.git.cloos@jhcloos.com> (raw)
One of the few irritations when using git — note that you’ll need a
relatively slow link to notice — is that the progress always shows
something .99 when under one Meg.
This patch eliminates the constant .99 from the progress display.
James Cloos (1):
Improve progress display in kB range.
progress.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next reply other threads:[~2009-04-19 4:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 4:38 James Cloos [this message]
2009-04-19 4:32 ` [PATCH 1/1] Improve progress display in kB range James Cloos
2009-04-21 4:56 ` Nicolas Pitre
2009-04-21 17:11 ` James Cloos
2009-04-21 17:28 ` Nicolas Pitre
2009-04-21 20:16 ` James Cloos
2009-04-22 14:33 ` James Cloos
2009-04-22 19:44 ` Junio C Hamano
2009-04-22 22:35 ` James Cloos
2009-04-23 6:23 ` Johannes Sixt
2009-04-24 20:15 ` James Cloos
2009-04-24 21:46 ` Nicolas Pitre
2009-04-24 22:20 ` James Cloos
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=cover.1240115957.git.cloos@jhcloos.com \
--to=cloos@jhcloos.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).