From: Daiane Angolini <daiane.angolini@freescale.com>
To: Christian Betz <christian.betz@gmail.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: making building master-next just a little bit easier
Date: Fri, 30 Aug 2013 16:35:46 -0300 [thread overview]
Message-ID: <5220F412.2000306@freescale.com> (raw)
In-Reply-To: <CAC9ffDH5GbEO5fxQxB1mCnz8h8bL8Sqka_T4_nSXx6-vH4B71A@mail.gmail.com>
> i'm not sure i was clear either. regarding the README:
>
> * the default branch on github when you go the project is the dylan
> branch, the README contains dylan in the instructions.
> * the master branch README contains dylan in the instructions:
> ** https://github.com/Freescale/fsl-community-bsp-platform/blob/master/README
> ** right now i consider myself a user, tester, and a developer. it's a
> convenience to have 'dylan', 'master' or 'master-next' show up in the
> instructions when I select a different branch from the dropdown in
> github
> *** this is because I am lazy and forgetful ;)
It made me think that maybe, have all the command lines would be better.
all the command lines, and a description of what is what:
dylan - latest stable branch, for production
$ lalalalalalal -b dylan
master - development branch, where things happens
$ alalaalalalal -b master
master-next - test branch, for fearless, intrepid developer
$ lalalala -b master-next
But, it also made me think that maybe we are overthinking this topic =P
>
> i'm going to forget about the README for now and will make a separate
> patch if my lazyness argument is convincing to anyone.
>
> to recap: ONE patch for default.xml without any README changes will be
> forthcoming tonight.
>
> --christian
--
Daiane
prev parent reply other threads:[~2013-08-30 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 17:36 making building master-next just a little bit easier Christian Betz
2013-08-27 17:53 ` Eric Nelson
2013-08-27 18:52 ` John Weber
2013-08-29 20:03 ` Otavio Salvador
2013-08-30 6:48 ` Christian Betz
2013-08-30 14:23 ` Daiane Angolini
2013-08-30 18:58 ` Christian Betz
2013-08-30 19:35 ` Daiane Angolini [this message]
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=5220F412.2000306@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=christian.betz@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.