Skip to content
This repository has been archived by the owner on Jun 16, 2018. It is now read-only.

Update requirements txt djangobakery #121

Conversation

jkokenge
Copy link

Updates requirements.txt from django-bakery=0.1 to django-bakery = 0.2.2 so the user can specify different s3cmd config files with the --config= flag. I don't understand why this commit contains all the commits I've made to my own master and not just the commit I made with the change to update-requirements-txt-djangobakery branch. I'm sending this as a test more than anything.

@palewire
Copy link
Contributor

I think some of your CSVs are in here. That what you're aiming for?

@jkokenge
Copy link
Author

No, my goal was for the pull request to be that final commit only: 568c0b1. That's the only commit I had made to the update-requirements-txt-djangobakery branch. I'm not sure why all those other commits came along for the ride. I went through with the pull just to see how things shook out. I'll just close it and try it again once I get things figured out.

@jkokenge jkokenge closed this Mar 17, 2014
@jkokenge jkokenge reopened this Mar 17, 2014
@jkokenge jkokenge closed this Mar 17, 2014
@palewire
Copy link
Contributor

Try making a fork or branch off the master of this repo and only making that one commit.

@jkokenge jkokenge deleted the update-requirements-txt-djangobakery branch March 17, 2014 23:55
@jkokenge
Copy link
Author

Yeah, that's a good idea. It seemed like a bad idea to be hacking away at a repo that was actively in use to push data into production anyway. I'll fork from my personal repo and use that as a development branch. I'm interested in getting this library up to date with Django 1.6 etc. So, I'll make that a goal. I've also got some other small fixes, ideas cooking too, as we use this more in production. As always, I appreciate the feedback.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants