From: jfabernathy <jfabernathy@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: Using stable releases from git
Date: Mon, 30 Jan 2012 18:05:17 -0500 [thread overview]
Message-ID: <4F27222D.7010302@gmail.com> (raw)
In-Reply-To: <4F2720B1.8070001@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On 01/30/2012 05:58 PM, Joshua Lock wrote:
> It's beginning to sound like we've caught some folks off guard by
> pushing changes to the edison branch of the poky repository in
> preparation for an upcoming edison point release.
>
> The named branches are development branches for the release, stable
> release development will be done in the named branch and we can't
> guarantee they will be issue free (though we intend them to be where
> possible).
>
> If you're looking to use a git checkout which matches the release
> tarballs you should checkout the tags for the releases. i.e. for Poky
> Edison-6.0/Yocto 1.1:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0
>
So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
Jim A
> Having suffered through a couple of stable cycles recently I
> anticipate that in future the release branches will be updated more
> frequently. This will make it even more important to use a tag, rather
> than a branch, to track the releases using git.
>
> Cheers,
> Joshua
[-- Attachment #2: Type: text/html, Size: 2104 bytes --]
next prev parent reply other threads:[~2012-01-30 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 22:58 Using stable releases from git Joshua Lock
2012-01-30 23:05 ` jfabernathy [this message]
2012-01-30 23:13 ` McClintock Matthew-B29882
2012-01-30 23:15 ` Joshua Lock
2012-01-30 23:32 ` jfabernathy
2012-01-31 4:38 ` Joshua Lock
2012-01-31 15:28 ` jfabernathy
2012-01-31 16:04 ` Joshua Lock
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=4F27222D.7010302@gmail.com \
--to=jfabernathy@gmail.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.