Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Official git mirror on github/gitorious?
Date: Sun, 30 Jan 2011 12:40:08 +0000	[thread overview]
Message-ID: <4D455C28.7010406@xora.org.uk> (raw)
In-Reply-To: <20110130123418.4e354145@widy.localdomain>

On 30/01/2011 10:34, Paul Sokolovsky wrote:
> Hello,
>
> On Sun, 30 Jan 2011 01:34:13 +0000
> Graeme Gregory <dp@xora.org.uk> wrote:
>
>> On 30/01/2011 00:28, Paul Sokolovsky wrote:
>>> Hello,
>>>
>>> Searching for "openembedded" on both github and gitorious give
>>> quite a few hits:
>>>
>>> http://github.com/search?langOverride=&q=openembedded&repo=&start_value=1&type=Repositories
>>> http://gitorious.org/search?q=openembedded
>>>
>>> Was there a thought to provide official mirrors on both (or one)
>>> services for the purpose of accounting forks?
>>>
>> There is an "official" Ångstrom mirror on gitorious.
>>
>> http://gitorious.org/+angstrom-distribution/angstrom/openembedded
> Yes, seeing it made me think that it would be nice to fork it via site
> means. Is there guarantee of upstream update time for it? Also, even
> then it seems like a 2nd-level fork, not forking a pure OE repo
> specially designed to keep track of offshots.
>
No we just update it sometime or other. But with git it doesn't really
matter I think.

I think you best option is to approach OE with a plan to run such
projects yourself and get the admins to put a crontab in for you which
does the update nightly or something like that.

Graeme




  reply	other threads:[~2011-01-30 12:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  0:28 Official git mirror on github/gitorious? Paul Sokolovsky
2011-01-30  1:34 ` Graeme Gregory
2011-01-30 10:34   ` Paul Sokolovsky
2011-01-30 12:40     ` Graeme Gregory [this message]
2011-01-30 16:12       ` Paul Sokolovsky
2011-01-30 16:44         ` Graeme Gregory
2011-01-30 22:09 ` Tom Rini
2011-01-30 23:21   ` Philip Balister

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=4D455C28.7010406@xora.org.uk \
    --to=dp@xora.org.uk \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=pmiscml@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