From: Otavio Salvador <otavio@ossystems.com.br>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Yocto Project 1.2 M4 schedule
Date: Thu, 12 Apr 2012 14:12:39 -0300 [thread overview]
Message-ID: <CAP9ODKqQVkXJcb1F_dxS3eapYn0GQ=ZFOKdQjrO3FvP+pWSB2g@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1soezt5BK0Qnx1Jda_uHXuFKiW9apSxXOu650SqcsqqKCA@mail.gmail.com>
On Thu, Apr 12, 2012 at 13:55, Khem Raj <raj.khem@gmail.com> wrote:
>> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags and branches. The objections I heard to that didn't make sense to me, but I see this as a purely technical matter where others see it as something different :)
>
> I think that string is fine as long as its just for yocto but I think
> for OE-Core we are going to do a General release
> so tagging that with something yocto project will be very confusing
> unless we plan to do different releases of OE-Core for general
> availability
> and yocto project. I dont think we have bandwidth for that. And since
> poky repository makes a copy of OE-Core metadata it can be tagged in
> yoctoproject specific tags
>
> since OE-Core is at center of all layers I would propose that other
> layers when tagged contain OE-Core's release tag in their own tags
> name
>
> so something like <layer-tag>-<OE-Core-tag its targetting>
I agree; yocto tag ought to be check in yocto git repository. What we
need is to have an OE-Core release at same time.
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
next prev parent reply other threads:[~2012-04-12 17:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 18:01 Yocto Project 1.2 M4 schedule Liu, Song
2012-04-11 0:51 ` Julian Pidancet
2012-04-12 9:02 ` Richard Purdie
2012-04-12 9:29 ` Koen Kooi
2012-04-12 14:24 ` Otavio Salvador
2012-04-12 14:39 ` Koen Kooi
2012-04-12 14:51 ` Eric Bénard
2012-04-12 15:45 ` McClintock Matthew-B29882
2012-04-12 18:28 ` Denys Dmytriyenko
2012-04-12 16:55 ` Khem Raj
2012-04-12 17:12 ` Otavio Salvador [this message]
2012-04-12 17:22 ` Koen Kooi
2012-04-12 17:32 ` Otavio Salvador
2012-04-12 18:31 ` Denys Dmytriyenko
2012-04-12 19:39 ` Flanagan, Elizabeth
2012-04-12 18:40 ` Richard Purdie
2012-04-12 19:20 ` Otavio Salvador
2012-04-12 19:46 ` Philip Balister
2012-04-12 19:57 ` Koen Kooi
2012-04-12 21:13 ` Denys Dmytriyenko
2012-04-12 21:16 ` Otavio Salvador
2012-04-12 21:29 ` Phil Blundell
2012-04-13 7:33 ` Andrei Gherzan
2012-04-13 10:58 ` Anders Darander
2012-04-12 19:31 ` Julian Pidancet
2012-04-12 19:41 ` Denys Dmytriyenko
2012-04-18 9:28 ` Koen Kooi
2012-04-18 10:18 ` Yocto Project Branch/Release Naming Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2012-04-09 17:59 Yocto Project 1.2 M4 schedule Liu, Song
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='CAP9ODKqQVkXJcb1F_dxS3eapYn0GQ=ZFOKdQjrO3FvP+pWSB2g@mail.gmail.com' \
--to=otavio@ossystems.com.br \
--cc=openembedded-core@lists.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.