From: "Tilo Schwarz" <tilo@tilo-schwarz.de>
To: "git.vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH RFC/RFD] clone: quell the progress report from init
Date: Thu, 25 Mar 2010 17:31:27 +0100 [thread overview]
Message-ID: <op.u94tipqya8ed4e@dellschleppa> (raw)
In-Reply-To: <7b9006620fab4214ee0db53ebc9e0caffc397959.1269506526.git.git@drmicha.warpmail.net>
On Thu, 25 Mar 2010 09:46:16 +0100, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Currently, cloning a local repository results in the progress report
> "Initialized empty Git repository in ..." from init but no other output,
> leaving the user to wonder what happened to the actual cloning.
/me, (as just being an interested git user reading this list), likes this
patch: As a Unix user I always wonder after a "git clone", why git tells
me something about an "empty Git repository" (I think I saw the same
message initializing submodules). I'd rather prefer no message, indicating
the command completed with success.
Regards,
Tilo
next prev parent reply other threads:[~2010-03-25 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 22:44 color (red) for error messages on all git commands Neal Kreitzinger
2010-03-24 22:58 ` Sverre Rabbelier
2010-03-24 23:12 ` Alex Riesen
2010-03-25 8:43 ` Michael J Gruber
2010-03-25 8:46 ` [PATCH RFC/RFD] clone: quell the progress report from init Michael J Gruber
2010-03-25 9:02 ` Alex Riesen
2010-03-25 9:26 ` Michael J Gruber
2010-03-25 16:31 ` Tilo Schwarz [this message]
2010-03-26 19:32 ` Junio C Hamano
2010-03-26 20:16 ` Nicolas Pitre
2010-03-26 20:24 ` Junio C Hamano
2010-03-30 5:18 ` Junio C Hamano
2010-03-30 8:05 ` Michael J Gruber
2010-03-30 8:43 ` Alex Riesen
2010-04-01 22:03 ` [PATCH] clone: quell the progress report from init and report on clone Michael J Gruber
2010-04-02 7:28 ` Junio C Hamano
2010-04-04 13:02 ` Michael J Gruber
2010-04-23 12:37 ` Michael J Gruber
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=op.u94tipqya8ed4e@dellschleppa \
--to=tilo@tilo-schwarz.de \
--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 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.