From: Muzaffer Tolga Ozses <tolga@ozses.net>
To: git@vger.kernel.org
Subject: Git reports
Date: Fri, 6 Dec 2013 18:51:47 +0200 [thread overview]
Message-ID: <CAMAQ3n+OtBdYALh4pg6kywtbgPtQjHr6Xc-2ff63df-h=TLwbA@mail.gmail.com> (raw)
Hi,
On another git server, I get reports like
Cloning into 'tcmb'...
remote: Counting objects: 704, done.
remote: Compressing objects: 100% (574/574), done.
remote: Total 704 (delta 369), reused 107 (delta 60)
Receiving objects: 100% (704/704), 129.99 KiB | 23 KiB/s, done.
Resolving deltas: 100% (369/369), done.
whereas I don't get those with my own. What could I be doing wrong?
Regards,
mto
next reply other threads:[~2013-12-06 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 16:51 Muzaffer Tolga Ozses [this message]
2013-12-06 17:00 ` Git reports Konstantin Khomoutov
2013-12-06 17:09 ` Konstantin Khomoutov
2013-12-06 17:44 ` Muzaffer Tolga Ozses
2013-12-06 17:50 ` Jeff King
2013-12-06 17:53 ` Konstantin Khomoutov
2013-12-06 19:19 ` Muzaffer Tolga Ozses
2013-12-06 19:24 ` Muzaffer Tolga Ozses
2013-12-06 19:26 ` Jonathan Nieder
2013-12-06 20:36 ` Junio C Hamano
2013-12-06 22:22 ` Jeff King
2013-12-07 19:46 ` Muzaffer Tolga Ozses
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='CAMAQ3n+OtBdYALh4pg6kywtbgPtQjHr6Xc-2ff63df-h=TLwbA@mail.gmail.com' \
--to=tolga@ozses.net \
--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).