[
https://issues.apache.org/jira/browse/JENA-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518605#comment-16518605
]
ASF GitHub Bot commented on JENA-1556:
--
Github user xristy commented on the issue:
Github user xristy commented on the issue:
https://github.com/apache/jena/pull/436
Thanks everyone. I seemed to have finally merged PR#436. I ended up using
@rvesse plus a bit from the commit workflow (which I agree should be linked on
the Contributing page):
> git
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/436
---
[
https://issues.apache.org/jira/browse/JENA-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518591#comment-16518591
]
ASF GitHub Bot commented on JENA-1556:
--
Github user asfgit closed the pull request at:
As for gitbox, the last result of my investigation was that we won't
_currently_ have the same JIRA integrations that we now have, because INFRA
hasn't done that yet. (And they would love to have some help doing that!)
I left the matter there. For my money, we might do well to revisit the JIRA
Thanks Andy, this is very helpful.
Best,
Aaron
> On Jun 20, 2018, at 6:02 AM, Andy Seaborne wrote:
>
> Aaron, Chris, all,
>
> One thing to mention - with the master repo on Apache hardware and PRs on the
> mirror (which we don't have write access to) there is a workflow for merging
> into
[
https://issues.apache.org/jira/browse/JENA-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518005#comment-16518005
]
ASF GitHub Bot commented on JENA-1556:
--
Github user kinow commented on the issue:
Github user kinow commented on the issue:
https://github.com/apache/jena/pull/436
The docs look really good! Only feedback I have:
* It's possible to avoid the empty commit, by amending the last commit
adding "this closes #123". That's what I normally do when I work in other
Aaron, Chris, all,
One thing to mention - with the master repo on Apache hardware and PRs
on the mirror (which we don't have write access to) there is a workflow
for merging into the Apache github repo:
https://cwiki.apache.org/confluence/display/JENA/Commit+Workflow+for+Github-ASF
Andy
Hi Andy,
Thanks for the response. Your suggestion worked and the query completed in a
similar time to the union graph approach.
I'd tried moving the filter into the graph clause but not swapping the graph
order.
I added that update on the documentation so if anyone else was having similar
[
https://issues.apache.org/jira/browse/JENA-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517984#comment-16517984
]
ASF GitHub Bot commented on JENA-1556:
--
Github user afs commented on the issue:
Github user afs commented on the issue:
https://github.com/apache/jena/pull/436
I have a copy of Jena cloned from git-wip-us.apache.org = a added second
remote for github (this is so it is called as "github", not the full URL
"https://github.com/apache/jena.git;).
To merge,
[
https://issues.apache.org/jira/browse/JENA-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517973#comment-16517973
]
ASF GitHub Bot commented on JENA-1556:
--
Github user afs commented on the issue:
Github user afs commented on the issue:
https://github.com/apache/jena/pull/436
Committer workflow:
https://cwiki.apache.org/confluence/display/JENA/Commit+Workflow+for+Github-ASF
---
[
https://issues.apache.org/jira/browse/JENA-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517938#comment-16517938
]
ASF GitHub Bot commented on JENA-1556:
--
Github user rvesse commented on the issue:
Github user rvesse commented on the issue:
https://github.com/apache/jena/pull/436
@xristy I think you can just merge as you would normally though you
probably need to be explicit about the remote and branch you are using for
remote operations:
```
> git checkout master
16 matches
Mail list logo
