<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 7, 2014 at 3:04 PM, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On Apr 7, 2014, at 8:57 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
<br>
> Hello Guys<br>
><br>
> We have started cookbook repositories for JaveScript [1], iOS [2] and Android[3]. As we go and add more features, we add demo app/recipe to them. But sometimes the demo app will not fit with the cookbook format. I think it’s still nice to have linked to it. For example, the upcoming Push-Helloworld and Push-Quickstart could be linked back to our cookbook repos.<br>
><br>
> For iOS, we have links in the README file, for JavaScript it’s gh linked repos. I actually like the idea fo gh sub-repo, and I’d like to use the same or iOS cookbook. wdyt?<br></div></blockquote><div><br></div><div>
+1 on linking/including via submodules</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
<br>
</div>+1<br>
<br>
the only thing i worried about when using sub-repos is that the user might mss the instructions on how to pull them down.<br></blockquote><div><br></div><div>yep, that's a valid concern</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> ++<br>
> Corinne<br>
> [1] <a href="https://github.com/aerogear/aerogear-js-cookbook" target="_blank">https://github.com/aerogear/aerogear-js-cookbook</a><br>
> [2] <a href="https://github.com/aerogear/aerogear-ios-cookbook" target="_blank">https://github.com/aerogear/aerogear-ios-cookbook</a><br>
> [3] <a href="https://github.com/aerogear/aerogear-android-cookbook" target="_blank">https://github.com/aerogear/aerogear-android-cookbook</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>