From: Petr Baudis <pasky@suse.cz>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Theodore Tso <tytso@mit.edu>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Alternates and push
Date: Tue, 9 Sep 2008 10:35:51 +0200 [thread overview]
Message-ID: <20080909083551.GA10544@machine.or.cz> (raw)
In-Reply-To: <20080906192106.GB18631@spearce.org>
On Sat, Sep 06, 2008 at 12:21:06PM -0700, Shawn O. Pearce wrote:
> 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.
But it should be used only in controlled environment. If you happen to
have permissions to write to the forkee, you can wipe out its refs with
git fetch --mirror (and if you don't happen to have permissions, it will
just fail, so currently you cannot use this on repo.or.cz forks,
unfortunately). If you don't make sure refs are never packed (I do on
repo.or.cz, historically because of dumb transports - do they support
packed refs by now?), this won't work either. Maybe there are other
considerations too.
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
next prev parent reply other threads:[~2008-09-09 8:37 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
2008-09-09 8:35 ` Petr Baudis [this message]
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=20080909083551.GA10544@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonsmirl@gmail.com \
--cc=spearce@spearce.org \
--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 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).