[GitHub] felix pull request: Possible fix for [FELIX-4436] https://issues.a...

2014-03-18 Thread barthel
Github user barthel closed the pull request at: https://github.com/apache/felix/pull/4 --- 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

Re: [GitHub] felix pull request: Possible fix for [FELIX-4436] https://issues.a...

2014-03-14 Thread Uwe Barthel
Hi Richard, To me, these pull request are sort of annoying, since we don't even use git for the Felix source repo... Apologies if I have annoyed you. You don't need any git experience to work with this pull request. https://github.com/apache/felix/pull/4.patch Use this link to

Re: [GitHub] felix pull request: Possible fix for [FELIX-4436] https://issues.a...

2014-03-14 Thread Richard Hall
It wasn't you personally that annoyed me, just the messages. I'd rather it be an automated system to attach a patch to a JIRA issue. My annoyance had nothing to do with git, which I use on other projects. On Mar 14, 2014 2:51 AM, Uwe Barthel bart...@x-reizend.de wrote: Hi Richard, To me,

[GitHub] felix pull request: Possible fix for [FELIX-4436] https://issues.a...

2014-03-13 Thread barthel
GitHub user barthel opened a pull request: https://github.com/apache/felix/pull/4 Possible fix for [FELIX-4436] https://issues.apache.org/jira/browse/FELIX-4436 * handle bundle if bundle location is a opaque uri * use 'file:' instead of last index of colon for extract the path

Re: [GitHub] felix pull request: Possible fix for [FELIX-4436] https://issues.a...

2014-03-13 Thread Richard S. Hall
To me, these pull request are sort of annoying, since we don't even use git for the Felix source repo... - richard On 3/13/14, 20:00 , barthel wrote: GitHub user barthel opened a pull request: https://github.com/apache/felix/pull/4 Possible fix for [FELIX-4436]