Rafael,
Will you update it or not (http://archive.apache.org/dist/qpid/proton/0.9/)?
When will it be announced?
--
Regards, Irina.
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/14#issuecomment-87687689
Ah, I actually missed the note about changing the filename entirely :)
Given that it wouldnt clash as I thought and would actually restore the
filename to it
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/14#issuecomment-87685628
*technically* we wouldn't have a name clash because of the .tgz --> .tar.gz
renaming, so people would only notice if they browsed the mirror filesystems
and saw both a .
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/14#issuecomment-87675670
As the archive has already been distributed via the mirror system, I think
updating the current named files would likely be considered bad form at this
point. I'm no
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/14#issuecomment-87664489
@rhs as we've not announced 0.9 on the website yet, it might be worth
re-creating the 0.9 release tar using the updated export.sh and re-uploading it?
---
If your proje
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-proton/pull/14
---
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
Github user rhs commented on the pull request:
https://github.com/apache/qpid-proton/pull/14#issuecomment-87651630
+1
---
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
GitHub user dnwe opened a pull request:
https://github.com/apache/qpid-proton/pull/14
NO-JIRA: export.sh creates pax-based tar
Having switched to using git-archive, we end up creating a tar that uses
the PAX-based scheme for supporting long pathnames. This causes issues
for a
