Martin, a quick question. To encourage people to contribute to documentation,
we added an "EDIT" button at the top right corner, which links you directly to
the github repo and page.
Looks like you wanted to help with documentation, but were having trouble with
it. Was the "EDIT" button confusi
Hi Martin
There file is located in the cordova-docs
https://github.com/apache/cordova-docs/blob/master/www/docs/en/6.x/guide/platforms/android/index.md
Go ahead and send a PR
On Mon, Feb 29, 2016 at 8:54 PM Martin Wheeler
wrote:
> Hi List,
>
> I'm not really sure if this should be sent in her
Hi List,
I'm not really sure if this should be sent in here but if someone could
point me in the right place that would be great too.
I found a spelling mistake on the Documentation page for the Android
Platform Guide.
https://cordova.apache.org/docs/en/latest/guide/platforms/android/index.html#
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-docs/pull/291
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
GitHub user robpaveza opened a pull request:
https://github.com/apache/cordova-docs/pull/291
Windows 10 documentation update
This is part of a migration from the Windows 10 experimental readme into
cordova-docs.
You can merge this pull request into a Git repository by running
Github user nikhilkh closed the pull request at:
https://github.com/apache/cordova-docs/pull/267
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-docs/pull/267#issuecomment-90735435
I'm OK with not changing the docs here. I'll close this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user agrieve commented on the pull request:
https://github.com/apache/cordova-docs/pull/267#issuecomment-90716706
Do we still want this change given that both gradle and ant-style are
accepted? I'm thinking no since I find gradle-style makes more sense. If so,
though, need to f
GitHub user nikhilkh opened a pull request:
https://github.com/apache/cordova-docs/pull/267
CB-8500 Documentation update for singing property name change
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-docs CB
Not sure. An idea is one branch per version? So if you work on master, that
is "edge". To grab a whole directory of version docs, write a script that
exports the contents of each branch (git-checkout-index) into a folder with
the same branch name (or mapped), then run joDoc (our current tool)
On
Are there plans for a "*for a saner doc system*" ?
--Carlos
On Mon, Jun 24, 2013 at 7:25 PM, Shazron wrote:
> Did a major update for previous versions. It's such a pain if we miss a doc
> update for a version X, and we're at version X+2.
>
> At master branch, you update for edge, X+2, X+1 and
Did a major update for previous versions. It's such a pain if we miss a doc
update for a version X, and we're at version X+2.
At master branch, you update for edge, X+2, X+1 and X folders.
At X+2 branch, you update for edge, X+2, X+1 and X folders.
At X+1 branch, you update for edge, X+1, and X fo
Thanks Shaz!
I was away for JSConf, so another contributor handled the cordova-docs
release for 2.8.0.
Michael
On Wed, Jun 19, 2013 at 1:46 PM, Shazron wrote:
> This commit that was tagged 2.8.0:
>
> https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=1d2fdf5a3344a554136c505
This commit that was tagged 2.8.0:
https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=1d2fdf5a3344a554136c505b162d1931e878daad
Does not occur in branch 2.8.x:
https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=shortlog;h=refs/heads/2.8.x
Nor does the tagged commit occ
Rhetorical question of course I am fixing this...
On Wed, Jun 19, 2013 at 1:36 PM, Shazron wrote:
> I noticed in cordova-docs, the 2.8.0 tag was tagged in a commit on master,
> but not in the 2.8.x branch. Furthermore, the commit that was tagged is not
> even in the 2.8.x branch. Do I fix this?
I noticed in cordova-docs, the 2.8.0 tag was tagged in a commit on master,
but not in the 2.8.x branch. Furthermore, the commit that was tagged is not
even in the 2.8.x branch. Do I fix this?
On Wed, Jun 19, 2013 at 11:51 AM, Shazron wrote:
> Makes sense. I'll cherry-pick my changes to the rele
Makes sense. I'll cherry-pick my changes to the relevant branches.
On Wed, Jun 19, 2013 at 11:45 AM, Michael Brooks
wrote:
> Hey guys,
>
> There is no denying that the release branch practice is a little odd for
> cordova-docs. This is because the cordova-docs repository versions
> everything by
Hey guys,
There is no denying that the release branch practice is a little odd for
cordova-docs. This is because the cordova-docs repository versions
everything by directory (a legacy approach that we will someday shift away
from).
I'll hunt down the release wiki article and update it, but here i
Yeah I'm interested in the flow as well. I think we published everything
again in older releases, not sure if we are still doing that going forward
On Tue, Jun 18, 2013 at 9:30 AM, Marcel Kinard wrote:
> On Jun 17, 2013, at 6:21 PM, Shazron wrote:
>
> > Should I bother? I know they will go in
On Jun 17, 2013, at 6:21 PM, Shazron wrote:
> Should I bother? I know they will go in edge. There are a couple of issues:
> https://issues.apache.org/jira/browse/CB-3753
> https://issues.apache.org/jira/browse/CB-3752
>
> Basically it's weird since if I added it to the 2.8.0 folder, it's not in
Should I bother? I know they will go in edge. There are a couple of issues:
https://issues.apache.org/jira/browse/CB-3753
https://issues.apache.org/jira/browse/CB-3752
Basically it's weird since if I added it to the 2.8.0 folder, it's not in
the 2.8.x branch, but is in master...
So for older vers
21 matches
Mail list logo
