Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Agreed, pardon my misread. Pulling this in now...only considering
documentation on partial matching.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Agreed, pardon my misread. Pulling this in now...only considering
documentation on partial matching.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
@chtompki Well, 216 is about disabling concatenated options, and 217 is
about disabling partial matching; my patch implements the latter, i.e, you
still have concatenated options, but can opt to
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
@chtompki Well, 216 is about disabling concatenated options, and 217 is
about disabling partial matching; my patch implements the latter, i.e, you
still have concatenated options, but can opt to
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Upon reading [CLI-216](https://issues.apache.org/jira/browse/CLI-216) and
[CLI-217](https://issues.apache.org/jira/browse/CLI-217), this pull request
looks like it resolves CLI-216 and not CLI-2
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Upon reading [CLI-216](https://issues.apache.org/jira/browse/CLI-216) and
[CLI-217](https://issues.apache.org/jira/browse/CLI-217), this pull request
looks like it resolves CLI-216 and not CLI-2
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Working on this now.
---
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
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Working on this now.
---
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
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
I'll try to get to it today.
---
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 an
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
I'll try to get to it today.
---
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 an
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
@chtompki Any progress on this one?
---
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
enab
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
@chtompki Any progress on this one?
---
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
enab
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
Hey :-) Any progress on this one? Anything I can do to make it go forward?
Greets!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
Hey :-) Any progress on this one? Anything I can do to make it go forward?
Greets!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
Yes, I did see that PosixParser was also a part of the patch, but I thought
not to touch it since it's marked as Deprecated (I would not expect changes to
deprecated classes as a user at least).
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
Yes, I did see that PosixParser was also a part of the patch, but I thought
not to touch it since it's marked as Deprecated (I would not expect changes to
deprecated classes as a user at least).
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Looking at
[CLI-217.patch](https://issues.apache.org/jira/secure/attachment/12568952/CLI-217.patch),
I was wondering if we shouldn't also include changes to `PosixParser`? The
changes would be
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Looking at
[CLI-217.patch](https://issues.apache.org/jira/secure/attachment/12568952/CLI-217.patch),
I was wondering if we shouldn't also include changes to `PosixParser`? The
changes would be
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Yes aside from the `.gitignore` changes, this all looks quite reasonable.
---
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
Github user chtompki commented on the issue:
https://github.com/apache/commons-cli/pull/15
Yes aside from the `.gitignore` changes, this all looks quite reasonable.
---
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
Github user britter commented on the issue:
https://github.com/apache/commons-cli/pull/15
@rubin55 sorry, I'm currently burried in work. Maybe @chtompki or @kinow
can have a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user britter commented on the issue:
https://github.com/apache/commons-cli/pull/15
@rubin55 sorry, I'm currently burried in work. Maybe @chtompki or @kinow
can have a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
Is someone looking at this PR?
---
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 a
Github user rubin55 commented on the issue:
https://github.com/apache/commons-cli/pull/15
Is someone looking at this PR?
---
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 a
Github user coveralls commented on the issue:
https://github.com/apache/commons-cli/pull/15
[](https://:/builds/12154396)
Coverage increased (+0.04%) to 96.287% when pulling
**3d9587caec7dd23d359bc112c63512e2bc3e0702 on
Github user coveralls commented on the issue:
https://github.com/apache/commons-cli/pull/15
[](https://:/builds/12154396)
Coverage increased (+0.04%) to 96.287% when pulling
**3d9587caec7dd23d359bc112c63512e2bc3e0702 on
Github user coveralls commented on the issue:
https://github.com/apache/commons-cli/pull/15
[](https://:/builds/12101592)
Coverage decreased (-0.1%) to 96.122% when pulling
**4f17a89ad04bcf718aeac43d202f8c261ce0b796 on r
Github user coveralls commented on the issue:
https://github.com/apache/commons-cli/pull/15
[](https://:/builds/12101592)
Coverage decreased (-0.1%) to 96.122% when pulling
**4f17a89ad04bcf718aeac43d202f8c261ce0b796 on r
28 matches
Mail list logo
