Incorporated pull request from Josh and Marcel, added the CB-7890 to
notable changes in the lib, bumped micro numbers for versions that will
have to be changed.

Published it in github/cordova/apache-blog-posts at
https://github.com/cordova/apache-blog-posts/blob/master/2014-11-10-tools-release.md
Please review.

Steve, thanks for adding me to the org.

Deleted my fork of the blog posts repo at github/kamrik.

On Mon, Nov 10, 2014 at 2:54 PM, Josh Soref <[email protected]> wrote:

> I'm assuming I can't push there either...
>
> On 11/10/14, 2:41 PM, "Steven Gill" <[email protected]> wrote:
>
> >Mark, I added you as owner to that Org.
> >
> >-Steve
> >
> >On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky <[email protected]>
> >wrote:
> >
> >> I got a permission denied error when trying to push to origin. Didn't
> >> invest the time to investigate it. Does this repo live on GitHub or is
> >>it
> >> only mirrored there?
> >> Cloned it using `grunt cloneBlog` according to instructions at
> >> https://svn.apache.org/repos/asf/cordova/site/README.md
> >>
> >> On Mon, Nov 10, 2014 at 1:00 PM, Marcel Kinard <[email protected]>
> >>wrote:
> >>
> >> > https://github.com/kamrik/apache-blog-posts/pull/2
> >> >
> >> > BTW, is there a reason to do the work on kamrik/master instead of
> >> > origin/topicBranch or origin/master? I think I have content from
> >> Parashuram
> >> > that you don't.
> >> >
> >> > On Nov 10, 2014, at 11:31 AM, Josh Soref <[email protected]>
> >>wrote:
> >> >
> >> > > To be fair, if you missed it, others will too, which argues that it
> >> > should
> >> > > be reorganized.
> >> > >
> >> > > I've done a PR for the other bits, but someone should consider this
> >> > point.
> >> > >
> >> > > On 11/10/14, 11:27 AM, "Marcel Kinard" <[email protected]> wrote:
> >> > >
> >> > >> Ah, missed that.
> >> > >>
> >> > >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky <[email protected]>
> >> > wrote:
> >> > >>
> >> > >>> The two items under "Platform updates" are already links to those
> >>two
> >> > >>> posts.
> >> >
> >> >
> >>
>
>

Reply via email to