From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] repo.or.cz now supports "project forks"
Date: Tue, 24 Oct 2006 06:52:01 +0200 [thread overview]
Message-ID: <20061024045201.GX20017@pasky.or.cz> (raw)
Hi,
FYI, the http://repo.or.cz/ public Git hosting now supports project
forking, which basically means that if you've done something cool to an
existing project and want to publish your work, you can create a "fork"
of the project on repo.or.cz and it will group nicely together in gitweb
and users will be hinted about the possibility to use --reference when
cloning your changes; also, repo.or.cz disk space will be conserved
thanks to the alternates mechanism. ;-)
The other main goal aside gitweb grouping wasn't achieved yet though -
greatly reduced push times. Hey, pushing Git to a new repository takes
inordinate amount of time (actually also mostly because all the objects are
unpacked on the remote side, which is silly as well), I didn't try pushing
Linux kernel to a fresh repository but it'll likely take ages. The idea
would be to make git-receive-pack take alternates into account when
announcing what commits does the server side have, but someone will need
to code up a patch for that...
It wasn't tested heavily, so please tell me about any warts you hit.
Thanks,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next reply other threads:[~2006-10-24 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 4:52 Petr Baudis [this message]
2006-10-24 17:39 ` [ANNOUNCE] repo.or.cz now supports "project forks" Petr Baudis
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=20061024045201.GX20017@pasky.or.cz \
--to=pasky@suse.cz \
--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