From: Carl Worth <cworth@cworth.org>
To: git@vger.kernel.org
Subject: git-push of new, tiny branch doing more work than necessary?
Date: Thu, 21 Sep 2006 15:29:04 -0700 [thread overview]
Message-ID: <87fyekkg5r.wl%cworth@cworth.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
I've run through something quite like the following scenario a few
times lately:
git pull origin
git checkout -b experiment
# hack a file or two
git commit -a -m "new experiment"
git push origin experiment
What I expect at this point is for git to push the few newly created
objects out to the repository. Instead it talks about generating,
deltifying, transferring, and unpacking thousands of objects (see
below).
Shouldn't the same WANT/HAVE hand shaking that makes git-fetch
efficient be doing something similar here? Or am I just doing
something wrong?
-Carl
$ git --version
git version 1.4.2.rc2.gef1d9
$ git push cworth 8379
updating 'refs/heads/8379'
from 0000000000000000000000000000000000000000
to 44379202da96faf632b73cdcdd6c0a74fb4b54f4
Generating pack...
Done counting 4900 objects.
Result has 4622 objects.
Deltifying 4622 objects.
100% (4622/4622) done
Unpacking 4622 objects
Total 4622, written 4622 (delta 3411), reused 1259 (delta 946)
refs/heads/8379: 0000000000000000000000000000000000000000 ->
44379202da96faf632b73cdcdd6c0a74fb4b54f4
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-09-21 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 22:29 Carl Worth [this message]
2006-09-21 22:34 ` git-push of new, tiny branch doing more work than necessary? Johannes Schindelin
2006-09-22 7:40 ` Andy Whitcroft
2006-09-28 18:10 ` Carl Worth
2006-09-22 2:31 ` Junio C Hamano
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=87fyekkg5r.wl%cworth@cworth.org \
--to=cworth@cworth.org \
--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).