From: Jason Merrill <jason@redhat.com>
To: Dmitrijs Ledkovs <dmitrij.ledkov@ubuntu.com>
Cc: git@vger.kernel.org
Subject: Re: How to fork on repo.or.cz?
Date: Thu, 06 May 2010 00:38:11 -0400 [thread overview]
Message-ID: <4BE247B3.8060704@redhat.com> (raw)
In-Reply-To: <x2r86ecb3c71004241233h97e3cf08l89aa4e6ef2fc4425@mail.gmail.com>
On 04/24/2010 03:33 PM, Dmitrijs Ledkovs wrote:
> Looking at this output it doesn't seem like my fork
> is reusing objects from the "fork parent" repo.
>
> What wrong? How am I suppose to use forks on repo.or.cz such that I
> upload just *my* commits and don't re-upload whole history again.
I have been having the same problem. I sent mail to admin@repo.or.cz
about it and got this reply:
> Thank you for the info. Unfortunately the server admin team is
> currently severely undermanned and there is noone to fix this (anyone
> interested in helping out would be gladly welcome), so all I could do
> for now is to add this to our TODO list.
Jason
next prev parent reply other threads:[~2010-05-06 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 19:33 How to fork on repo.or.cz? Dmitrijs Ledkovs
2010-05-06 4:38 ` Jason Merrill [this message]
2010-05-06 9:51 ` Dmitrijs Ledkovs
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=4BE247B3.8060704@redhat.com \
--to=jason@redhat.com \
--cc=dmitrij.ledkov@ubuntu.com \
--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;
as well as URLs for NNTP newsgroup(s).