From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Personal git repositories
Date: Wed, 27 Apr 2011 11:14:58 -0700 [thread overview]
Message-ID: <1303928099.2242.2.camel@scimitar> (raw)
In-Reply-To: <4DB8506B.9000709@intel.com>
On Wed, 2011-04-27 at 10:20 -0700, Elizabeth Flanagan wrote:
> A few notes, since I talked with Darren about this earlier.
>
> As one of the people in charge of maintaining the git repo, I would like to avoid having, as Darren suggested, a whole
> bunch of -contrib repos. However, maybe I'm missing something here, as I think basic git solves this issue:
I don't agree. I have a few sparse layers and some other code that I am
not sharing because they need repositories *somewhere*.
Having said that some of these recipes may be useful to others yet
definitely don't belong in oe-core. What do I do with them? The
mechanism Darren describes seems like it would work for my use case.
Cheers,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-27 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 3:00 Personal git repositories Darren Hart
2011-04-27 3:22 ` Bruce Ashfield
2011-04-27 3:57 ` Darren Hart
2011-04-27 4:37 ` Saul Wold
2011-04-27 4:56 ` Darren Hart
2011-04-27 4:39 ` Tom Zanussi
2011-04-27 4:53 ` Darren Hart
2011-04-27 5:05 ` Tom Zanussi
2011-04-27 6:35 ` Darren Hart
2011-04-27 7:56 ` Koen Kooi
2011-04-27 14:45 ` Darren Hart
2011-04-27 17:20 ` Elizabeth Flanagan
2011-04-27 18:14 ` Joshua Lock [this message]
2011-04-27 18:29 ` Elizabeth Flanagan
2011-04-27 21:03 ` Richard Purdie
2011-04-27 22:47 ` Darren Hart
2011-04-28 0:59 ` Bruce Ashfield
2011-04-28 3:12 ` Xianghua Xiao
2011-04-28 8:28 ` Richard Purdie
2011-04-28 14:56 ` Bruce Ashfield
2011-04-28 17:07 ` Darren Hart
2011-04-29 4:04 ` Darren Hart
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=1303928099.2242.2.camel@scimitar \
--to=josh@linux.intel.com \
--cc=yocto@yoctoproject.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 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.