From: Junio C Hamano <gitster@pobox.com>
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>
Subject: Re: [PATCH] doc: fast-import: contextualize the hardware cost
Date: Fri, 01 Aug 2025 07:44:18 -0700 [thread overview]
Message-ID: <xmqqo6szm799.fsf@gitster.g> (raw)
In-Reply-To: <a9bc7547a27aab8bc2404caeb821b7f5c4c10d14.1754055658.git.code@khaugsbakk.name> (kristofferhaugsbakk@fastmail.com's message of "Fri, 1 Aug 2025 15:42:25 +0200")
kristofferhaugsbakk@fastmail.com writes:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> 6e411d20440 (Initial draft of fast-import documentation., 2007-02-05)
> pointed out how much time a fast-import took on some hardware with a
> specific cost. Let’s further point out that this experiment was done
> in 2007. So modern hardware should have no issues with such a repo.
>
> Also move the parenthetical to the end now that it contains four words.
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
> ---
> Documentation/git-fast-import.adoc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-fast-import.adoc b/Documentation/git-fast-import.adoc
> index d2327842003..6f9763c11b3 100644
> --- a/Documentation/git-fast-import.adoc
> +++ b/Documentation/git-fast-import.adoc
> @@ -182,7 +182,7 @@ amount of memory usage and processing time. Assuming the frontend
> is able to keep up with fast-import and feed it a constant stream of data,
> import times for projects holding 10+ years of history and containing
> 100,000+ individual commits are generally completed in just 1-2
> -hours on quite modest (~$2,000 USD) hardware.
> +hours on quite modest hardware (~$2,000 USD in 2007).
That is a definite improvement. Thanks.
prev parent reply other threads:[~2025-08-01 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 13:42 [PATCH] doc: fast-import: contextualize the hardware cost kristofferhaugsbakk
2025-08-01 14:44 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo6szm799.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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 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).