From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>, git@vger.kernel.org
Subject: Re: Users of git-check-files?
Date: Wed, 03 Aug 2005 10:30:21 -0700 [thread overview]
Message-ID: <7vy87jc4ia.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200508031908.22562.Josef.Weidendorfer@gmx.de> (Josef Weidendorfer's message of "Wed, 3 Aug 2005 19:08:22 +0200")
Josef Weidendorfer <Josef.Weidendorfer@gmx.de> writes:
> ~/tmp/git/clone2> cg-push
> 'refs/heads/branch2': updating from 80e4d426dd4c865b943cc1121b580a946eee921d
> to 8196067677e3415ce404ea5bc35731ac7d56115d
> fatal: bad object f7e944b036fd00af656b262140c1dc93ceffadb1
> Packing 0 objects
> Unpacking 0 objects
Ahhhh.
Yes, we read from the remote and use old->sha1 when doing the
pack generation. If we do not have that object (in Josef's
example because it is not something we have pulled yet), then
rev-list has no way to create the necessary pack.
I have a feeling this explains what I've been seeing as well.
The first thing I do before I push is to fetch (but not
merge-pull) from kernel.org, but this happens against
www.kernel.org (to make sure people are seeing what I want them
to see), not against master. So if I happen to do my push cycle
twice before the things propagate from master to www.kernel.org,
_and_ if I happened to have run git prune in my private
repository just before the second cycle, I may end up not having
the objects referenced by "pu" branch there in my private
repository.
next prev parent reply other threads:[~2005-08-03 17:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 23:10 Users of git-check-files? Johannes Schindelin
2005-08-03 2:43 ` Linus Torvalds
2005-08-03 6:17 ` Junio C Hamano
2005-08-03 14:21 ` Johannes Schindelin
2005-08-03 18:00 ` Linus Torvalds
2005-08-03 22:09 ` Johannes Schindelin
2005-08-03 15:09 ` Linus Torvalds
2005-08-03 15:51 ` Junio C Hamano
2005-08-03 16:17 ` Linus Torvalds
2005-08-03 16:36 ` Junio C Hamano
2005-08-03 16:45 ` Linus Torvalds
2005-08-03 16:50 ` Johannes Schindelin
2005-08-03 17:08 ` Josef Weidendorfer
2005-08-03 17:30 ` Junio C Hamano [this message]
2005-08-03 17:46 ` Josef Weidendorfer
2005-08-03 18:08 ` Linus Torvalds
2005-08-03 23:25 ` [PATCH] (preview) Renaming push Junio C Hamano
2005-08-03 23:48 ` Linus Torvalds
2005-08-04 0:05 ` Junio C Hamano
2005-08-04 0:13 ` Linus Torvalds
2005-08-04 1:02 ` Junio C Hamano
2005-08-04 5:26 ` Junio C Hamano
2005-08-04 5:42 ` Linus Torvalds
2005-08-04 8:09 ` Junio C Hamano
2005-08-04 9:34 ` [PATCH] Teach rev-list since..til notation Junio C Hamano
2005-08-03 18:02 ` Users of git-check-files? Linus Torvalds
2005-08-03 17:02 ` Junio C Hamano
2005-08-03 17:23 ` Linus Torvalds
2005-08-03 17:37 ` Junio C Hamano
2005-08-03 17:46 ` Josef Weidendorfer
2005-08-03 18:10 ` Linus Torvalds
2005-08-03 17:48 ` Linus Torvalds
2005-08-03 18:07 ` Junio C Hamano
2005-08-03 18:31 ` Josef Weidendorfer
2005-08-03 16:46 ` Johannes Schindelin
2005-08-04 20:59 ` Junio C Hamano
2005-08-04 21:10 ` Johannes Schindelin
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=7vy87jc4ia.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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.