From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Theodore Tso <tytso@mit.edu>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Alternates and push
Date: Sat, 6 Sep 2008 12:21:06 -0700 [thread overview]
Message-ID: <20080906192106.GB18631@spearce.org> (raw)
In-Reply-To: <9e4733910809061124r3759ea79sda98b549df3e6e58@mail.gmail.com>
Jon Smirl <jonsmirl@gmail.com> wrote:
> On 9/6/08, Junio C Hamano <gitster@pobox.com> wrote:
> > Theodore Tso <tytso@MIT.EDU> writes:
> >
> > > 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.
> >
> >
> > This comes from an early (mis)design of git.
>
> What happens if I set a remote in my github digispeaker repo pointing
> to github's linus repo and the set a chron script to fetch it once a
> day? The alternates link is still in place.
github should do what repo.or.cz does:
ln -s .../linus.git/refs digispeaker.git/refs/forkee
That way the refs available in Linus' tree are also available
in your tree as Git will transparently follow the symlink.
However you have to be careful to make sure `git pack-refs` isn't
run with `--all --prune` as it will delete the refs from linus.git
when executed in digispeaker.git. Fun times when I did that to my
own repository one day. ;-)
Though we probably should fix Git to be somewhat smarter. But
until that stable binary is available, the symlink trick above
is a good work around.
--
Shawn.
next prev parent reply other threads:[~2008-09-06 19:22 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
2008-09-06 18:06 ` Junio C Hamano
2008-09-06 18:24 ` Jon Smirl
2008-09-06 19:21 ` Shawn O. Pearce [this message]
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=20080906192106.GB18631@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonsmirl@gmail.com \
--cc=tytso@mit.edu \
/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.