Hi Matt & all

Thanks a lot for looking after s3cmd and once again my apologies for not being active in the community. I'm really happy to see s3cmd is alive and well.

I have merged the mdomsch/s3cmd/merge branch to s3tools/s3cmd/master and released it as
s3cmd 1.5.0-beta1 (https://sourceforge.net/projects/s3tools/files/s3cmd-1.5.0-beta1.tar.gz). Please download, test and report back your success.

Matt - Quite a long time ago I made you an admin of the github repo (s3tools/s3cmd) and just recently also gave you admin access to the SourceForge s3tools project so you can merge directly to the official master and make new releases if you wish. There are a few steps involved, we can discuss that offline if you're keen. Or keep updating your merge branch and ping me when it's ready for a release, I'm sure I can find the time to roll out a release when the code is ready. I just don't have enough time for the day to day participation.

Thanks a lot for all your contributions guys, keep up the good work! And special thanks to Matt for putting it all together :)

Michal

On 27/11/13 04:50, Matt Domsch wrote:
The pull requests have been piling up for several months, with lots of
bugs being fixed by 21 different developers.  Michal hasn't had time
to review, test, and merge these, so here's my attempt to help the
process along, in hope of getting more people to test and report success/failure.

Appended is the shortlog of all changes pulled into my merge branch since
the current upstream-master 9ee3bdd320c8.  I've also tried leaving a
comment on each of the existing pull requests.  There were a few I
think need a little more work before they can be merged, or that
require Michal's judgment.

The tree: https://github.com/mdomsch/s3cmd/tree/merge
  (HEAD commit ae6030cd33d4)
ZIP archive: https://github.com/mdomsch/s3cmd/archive/merge.zip
Clone:   git clone git://github.com/mdomsch/s3cmd.git
  (you want the branch called 'merge')

If this works for you, please leave a comment.  If you were
particuarly affected by a bug that is now fixed, _please_ let us know
that as well.

Special thanks to Will Tinsdeall (@ivebeenlinuxed) for reviewing and
merging six of these patches into his tree for testing this last month.

Thanks,
Matt Domsch (@mdomsch)