From: Theodore Tso <tytso@MIT.EDU>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Alternates and push
Date: Sat, 6 Sep 2008 12:20:30 -0400 [thread overview]
Message-ID: <20080906162030.GT9129@mit.edu> (raw)
In-Reply-To: <9e4733910809060542s5ede6d6m5bdb894c958ea8b7@mail.gmail.com>
On Sat, Sep 06, 2008 at 08:42:50AM -0400, Jon Smirl wrote:
> At github my repo, digispeaker, has an alternate pointing to github's
> local copy of Linus' tree. I ignored my tree for a month and then
> pushed to it including 200MB of objects from Linus' tree. These 200MB
> of objects were pushed up to the server, but these objects were
> already in the alternates repository.
>
> What's supposed to happen? Is something broken in github's setup, or
> does pushing not take into account alternates?
Long-standing mis-feature in git's logic in deciding what to push.
It's been reported a few times, but apparently it's hard to fix, or at
least it never hsa been fixed as far as I know.
I work around it by ssh'ing into master.kernel.org and doing a "git
branch -f origin <commit-id-of-master-on-linus's-tree>". As long as
there is one branch which is up-to-date, git will avoid pushing a huge
number of objects to master.kernel.org. Of course, this workaround
only works if you have shell access....
- Ted
next prev parent reply other threads:[~2008-09-06 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 12:42 Alternates and push Jon Smirl
2008-09-06 16:20 ` Theodore Tso [this message]
2008-09-06 18:06 ` Junio C Hamano
2008-09-06 18:24 ` Jon Smirl
2008-09-06 19:21 ` Shawn O. Pearce
2008-09-09 8:35 ` Petr Baudis
2008-09-09 14:57 ` Shawn O. Pearce
2008-09-07 18:49 ` Jan Hudec
2008-09-07 18:56 ` Junio C Hamano
2008-09-07 19:17 ` Jan Hudec
2008-09-07 19:18 ` Junio C Hamano
2008-09-08 17:56 ` Jan Hudec
2008-09-07 23:41 ` Theodore Tso
2008-09-08 0:02 ` Junio C Hamano
2008-09-08 0:41 ` Theodore Tso
2008-09-08 2:53 ` Junio C Hamano
2008-09-08 5:07 ` Junio C Hamano
2008-09-08 6:42 ` Junio C Hamano
2008-09-08 7:24 ` Daniel Barkalow
2008-09-08 14:56 ` Shawn O. Pearce
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=20080906162030.GT9129@mit.edu \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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).