From: Jakub Narebski <jnareb@gmail.com>
To: sparse@infidigm.net
Cc: git@vger.kernel.org
Subject: Re: [Patch] Prevent cloning over http from spewing
Date: Wed, 03 Jun 2009 03:39:11 -0700 (PDT) [thread overview]
Message-ID: <m3vdnda9f7.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090602174229.GA14455@infidigm.net>
sparse@infidigm.net writes:
> When cloning over http git spews a bunch of hashs that don't really convey much.
> The attached patch disables them unless --verbose is specified.
>
Please follow guidelines stated in Documentation/SubmittingPatches:
* it is preferred to have patch inline, rather than as attachement
* put comments between "---" and the diffstat
Also please do the following:
* use git-format-patch output rather than that of git-show to
generate patch to send.
Also "Prevent cloning over http from spewing" is not, in my opinion,
good description; "Make cloning over http non-verbose by default"
would be better.
Finally a question: if we turn off verbose output, do we have any kind
of progress info fot git-clone over http?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-06-03 10:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 17:42 [Patch] Prevent cloning over http from spewing sparse
2009-06-03 10:21 ` Erik Faye-Lund
2009-06-03 10:39 ` Jakub Narebski [this message]
2009-06-03 18:28 ` Junio C Hamano
2009-06-03 19:10 ` Jeff King
2009-06-03 19:15 ` Shawn O. Pearce
2009-06-03 19:24 ` Jeff King
2009-06-03 19:32 ` Shawn O. Pearce
2009-06-03 19:44 ` Jeff King
2009-06-03 19:52 ` Shawn O. Pearce
2009-06-04 12:45 ` Tay Ray Chuan
2009-06-04 16:01 ` Jeff King
2009-06-07 10:31 ` Tay Ray Chuan
2009-06-07 11:21 ` Tay Ray Chuan
2009-06-08 12:24 ` Jeff King
2009-06-10 14:03 ` Tay Ray Chuan
2009-06-10 14:07 ` Tay Ray Chuan
2009-06-11 11:11 ` Jeff King
2009-06-22 12:10 ` Tay Ray Chuan
2009-07-20 15:24 ` Tay Ray Chuan
2009-06-08 11:54 ` Jeff King
2009-06-07 11:25 ` Tay Ray Chuan
2009-06-05 0:17 ` Jakub Narebski
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=m3vdnda9f7.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=sparse@infidigm.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.
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).