Github user bodewig commented on the pull request:
https://github.com/apache/commons-compress/pull/3#issuecomment-151728703
Don't feel forced to create a pull request just because we are using git
now. The established workflow of attaching a patch to JIRA is still in place.
Whatever
Github user beargiles closed the pull request at:
https://github.com/apache/commons-compress/pull/3
---
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 feat
Github user beargiles commented on the pull request:
https://github.com/apache/commons-compress/pull/3#issuecomment-151670553
Let me know what you need me to do. I've never done branching and merging
with git before, much less across projects, so I'm pretty much fumbling at this
point
Github user bodewig commented on the pull request:
https://github.com/apache/commons-compress/pull/3#issuecomment-151607463
Oops, this looks bigger than intended :-)
It seems as if out migration to git has made the wrong branch the default
branch. I'll ask the ASF infra team
GitHub user beargiles opened a pull request:
https://github.com/apache/commons-compress/pull/3
PKZip crypto header extensions
Addition of five classes that recognize PKZip crypto header extensions.
Actual encryption is not supported at this time, this patch is solely so users
can i
