review in the staging web site. Or even preview
> in GitHub pages as well.
>
> The decision for JBake was already done when I joined, so I just helped with
> a few issues. It works quite well though. But if ASF Infra is able to build a
> Jekyll project, then we could use it in
issues. It works quite well though. But if ASF Infra is able to build a
Jekyll project, then we could use it instead.
Bruno
From: Andy Seaborne
To: dev@jena.apache.org
Sent: Monday, 23 October 2017 3:09 AM
Subject: Re: github stuff Was: [2/2] jena git commi
y, 23 October 2017 3:09 AM
Subject: Re: github stuff Was: [2/2] jena git commit: JENA-1391: adding isEmpty
method to Dataset
Is there a git+CMS option? (or mirro git to SVN then ...)
CMS may not be around forever, and while the markdown isn't all
standard, it's quite close. (e.g.
Is there a git+CMS option? (or mirro git to SVN then ...)
CMS may not be around forever, and while the markdown isn't all
standard, it's quite close. (e.g. the processor "Title:" stuff)
I don't know what processor is behind CMS - python based? Home
grown/modified?
I've use jekyll (choice
On 16/10/17 14:12, aj...@apache.org wrote:
Andy Seaborne wrote on 10/13/17 3:40 PM:
If anyone is interesting in following it up, I have read that Apache
projects can now use gitbox where by all work is on
Github, including the full PR cycle, and the ASF is mirrored back. To
us, it looks lik
A few months ago I helped setting up OpenNLP's new website building from github.
The source is in an opennlp-site git repository, and is built with maven using
the maven jbake static site generator.
Before they were using the svn cms pubsub if I recall correctly. Maybe we could
have something s
Andy Seaborne wrote on 10/13/17 3:40 PM:
If anyone is interesting in following it up, I have read that Apache projects
can now use gitbox where by all work is on
Github, including the full PR cycle, and the ASF is mirrored back. To us, it
looks like the GH is the master and ASF
the mirror (II
The SHA1 is different.
The previous commit to rebased commit has changed so the SHA1 is
different. It is a different commit, some different metadata, with the
same patch.
On 13/10/17 17:17, aj...@apache.org wrote:
I did exactly that -- rebase branch over master, merge branch into
master, and
I did exactly that -- rebase branch over master, merge branch into master, and push to apache:master (which is what I
usually do). I see them being different than the commits in the PR, but I can't see for the life of me why...
Anyway, I force-pushed to the PR-- that seems to have closed it.
aj
