All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: git master not updating
Date: Wed, 1 Oct 2008 14:36:35 -0700	[thread overview]
Message-ID: <20081001213635.GF3010@smtp.west.cox.net> (raw)
In-Reply-To: <gc0lv9$46r$1@ger.gmane.org>

On Wed, Oct 01, 2008 at 10:18:49PM +0200, Koen Kooi wrote:
> On 01-10-2008 20:43, Tom Rini wrote:
>> On Wed, Oct 01, 2008 at 07:17:57PM +0200, Koen Kooi wrote:
[snip]
>>> All org.openembedded.* branches are still being updated.
>>
>> So is the answer that the "master" branch in git it not planned on being
>> used?  Or it will have some other use, documented over in ... ?  It
>> sounds like the problem is that the policy on what to use in the git
>> tree isn't published yet.  Or it is, and someone didn't read it.
>
> The only supported way to use OE is via monotone, if you are using a  
> makefile that's using something else you are SOL

I'm not using a Makefile.  I'd just like to know what part of git I
should be look at checking out and attempting to work in, as the
transition is apparently imminent.  I'm assuming that once the
transition is complete, there'll be documentation saying "If you want
the dev branch, do ...", "If you want the stable branch, do ...".  Does
this type of documentation not yet exist?  Is there still some debate as
to if the git master branch will be the dev branch, or if the naming
scheme of org.openembedded.{dev,stable}, etc will continue?  Thanks.

-- 
Tom Rini



  reply	other threads:[~2008-10-01 21:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 12:24 git master not updating Kalev Lember
2008-10-01 12:45 ` Otavio Salvador
2008-10-01 13:07   ` Kalev Lember
2008-10-01 13:18     ` Otavio Salvador
2008-10-01 13:34     ` Nicola Mfb
2008-10-01 14:24       ` Koen Kooi
2008-10-01 15:48         ` Mike (mwester)
2008-10-01 16:39           ` Andrea Adami
2008-10-01 17:13           ` Philip Balister
2008-10-01 18:32             ` Nicola Mfb
2008-10-01 23:33             ` Rod Whitby
2008-10-01 17:17           ` Koen Kooi
2008-10-01 18:11             ` Mike (mwester)
2008-10-01 18:43             ` Tom Rini
2008-10-01 20:18               ` Koen Kooi
2008-10-01 21:36                 ` Tom Rini [this message]
2008-10-01 23:57                   ` Rod Whitby
2008-10-01 23:30         ` Rod Whitby
2008-10-02  0:43           ` I'm sick of that Was " Holger Freyther
2008-10-02  1:50             ` Otavio Salvador
2008-10-02  1:51             ` Rod Whitby
2008-10-02 11:49             ` Cliff Brake
2008-10-02 12:51               ` Kalev Lember
2008-10-02 18:06             ` Mark Vels
2008-10-02 20:29               ` Rodrigo Vivi
2008-10-02 22:15             ` Michael Krelin
2008-10-02  0:36 ` Holger Freyther
2008-10-02 11:28   ` Cliff Brake
2008-10-03  2:55     ` Holger Freyther

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=20081001213635.GF3010@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.