[
https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540392#comment-14540392
]
ASF subversion and git services commented on PROTON-868:
Commit
On Tue, May 12, 2015 at 02:10:59PM -0400, Alan Conway wrote:
On Mon, 2015-05-11 at 09:36 -0400, Darryl L. Pierce wrote:
master-branch $ git merge --ff-only task-branch
That will refuse to merge unless the merge is a fast-forward, which is
the simple copy my commits to the end of trunk
On Mon, 2015-05-11 at 09:36 -0400, Darryl L. Pierce wrote:
On Mon, May 11, 2015 at 09:23:27AM -0400, Darryl L. Pierce wrote:
A request for all, please avoid doing merge commits on your Git repo.
When these hit the shared repo it can cause Git to try and fix [1] the
commit when rebasing.
[
https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540448#comment-14540448
]
ASF subversion and git services commented on PROTON-868:
Commit
On Tue, May 12, 2015 at 11:12:40AM -0400, Rafael Schloming wrote:
I made a bunch of line comments.
Things appear to be working in the scaled back example except for one
thing: when retrieving the record with pn_record_get the Swig wrapper
returned is of type SWIG:TYPE_p_void rather than the
[
https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540400#comment-14540400
]
ASF subversion and git services commented on PROTON-868:
Commit
On Tue, May 12, 2015 at 04:10:54PM -0400, Darryl L. Pierce wrote:
On Tue, May 12, 2015 at 11:12:40AM -0400, Rafael Schloming wrote:
I made a bunch of line comments.
Things appear to be working in the scaled back example except for one
thing: when retrieving the record with pn_record_get the
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540725#comment-14540725
]
ASF subversion and git services commented on PROTON-877:
Commit
On Mon, May 11, 2015 at 3:49 PM, Alan Conway acon...@redhat.com wrote:
On Thu, 2015-05-07 at 15:53 -0400, Rafael Schloming wrote:
I believe where we ended up was standardizing on a single snprintf-style
signature for all encode functions, i.e.:
// always returns encoded size, never
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-proton/pull/25
---
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 is
[
https://issues.apache.org/jira/browse/PROTON-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540952#comment-14540952
]
ASF subversion and git services commented on PROTON-827:
Commit
On Thu, 2015-05-07 at 15:42 -0400, Rafael Schloming wrote:
1. For developing new language bindings (and really for any development
work that will involve enough new stuff to have a noisy commit history)
we
use branches. This is already the case with the Ruby/C++/Python3
bindings,
[
https://issues.apache.org/jira/browse/PROTON-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540958#comment-14540958
]
ASF subversion and git services commented on PROTON-827:
Commit
On Tue, May 12, 2015 at 05:45:20AM -0400, Rafael Schloming wrote:
Can you post an isolated reproducer with just your definition of pn_rbkey_t
and a code version of the 5 steps that lead to the seg fault?
On my PROTON-781-reactive-ruby-apis branch is an example named
On Tue, May 12, 2015 at 09:44:41AM -0400, Rafael Schloming wrote:
On Tue, May 12, 2015 at 8:34 AM, Darryl L. Pierce dpie...@redhat.com
wrote:
On Tue, May 12, 2015 at 05:45:20AM -0400, Rafael Schloming wrote:
Can you post an isolated reproducer with just your definition of
pn_rbkey_t
Can you post an isolated reproducer with just your definition of pn_rbkey_t
and a code version of the 5 steps that lead to the seg fault?
--Rafael
On Mon, May 11, 2015 at 5:21 PM, Darryl L. Pierce dpie...@redhat.com
wrote:
On Thu, May 07, 2015 at 01:02:13PM -0400, Rafael Schloming wrote:
On Tue, May 12, 2015 at 8:34 AM, Darryl L. Pierce dpie...@redhat.com
wrote:
On Tue, May 12, 2015 at 05:45:20AM -0400, Rafael Schloming wrote:
Can you post an isolated reproducer with just your definition of
pn_rbkey_t
and a code version of the 5 steps that lead to the seg fault?
On my
On Tue, May 12, 2015 at 11:12:40AM -0400, Rafael Schloming wrote:
I made a bunch of line comments.
Excellent, thanks for that. I'll update the code and reply with my
results.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value
On Tue, May 12, 2015 at 10:34 AM, Darryl L. Pierce dpie...@redhat.com
wrote:
On Tue, May 12, 2015 at 09:44:41AM -0400, Rafael Schloming wrote:
On Tue, May 12, 2015 at 8:34 AM, Darryl L. Pierce dpie...@redhat.com
wrote:
On Tue, May 12, 2015 at 05:45:20AM -0400, Rafael Schloming wrote:
19 matches
Mail list logo