From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Nicolas Pitre <nico@cam.org>, git@vger.kernel.org
Subject: Re: [PATCH 1/6] more compact progress display
Date: Wed, 17 Oct 2007 02:37:27 -0400 [thread overview]
Message-ID: <20071017063727.GX13801@spearce.org> (raw)
In-Reply-To: <4715ACE4.9080907@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> wrote:
> Nicolas Pitre schrieb:
> >- start_progress_delay(&progress, "Checking %u files out...",
> >- "", total, 50, 2);
> >+ start_progress_delay(&progress, "Checking files out",
> >+ total, 50, 2);
>
> While you are here, could you make that "Checking out files", please?
I'll amend it right now. I'm finishing up building my nightly
update to git/spearce.git and this is about to go into next.
So... you just caught me in time to do an amend. :-)
--
Shawn.
prev parent reply other threads:[~2007-10-17 6:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 1:55 [PATCH 0/6] miscelaneous stuff Nicolas Pitre
2007-10-17 1:55 ` [PATCH 1/6] more compact progress display Nicolas Pitre
2007-10-17 1:55 ` [PATCH 2/6] cope with multiple line breaks within sideband progress messages Nicolas Pitre
2007-10-17 1:55 ` [PATCH 3/6] pack-objects: no delta possible with only one object in the list Nicolas Pitre
2007-10-17 1:55 ` [PATCH 4/6] pack-objects.c: fix some global variable abuse and memory leaks Nicolas Pitre
2007-10-17 1:55 ` [PATCH 5/6] fix const issues with some functions Nicolas Pitre
2007-10-17 1:55 ` [PATCH 6/6] fix for more minor memory leaks Nicolas Pitre
2007-10-17 2:15 ` Deltifying? (was [PATCH 3/6] pack-objects: no delta possible...) Shawn O. Pearce
2007-10-17 2:28 ` Nicolas Pitre
2007-10-17 2:11 ` [PATCH 1/6] more compact progress display Shawn O. Pearce
2007-10-17 2:24 ` Nicolas Pitre
2007-10-17 8:20 ` Karl Hasselström
2007-10-17 20:56 ` Nicolas Pitre
2007-10-18 4:58 ` Shawn O. Pearce
2007-10-18 8:34 ` Karl Hasselström
2007-10-17 6:34 ` Johannes Sixt
2007-10-17 6:37 ` Shawn O. Pearce [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071017063727.GX13801@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=nico@cam.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).