Skip to content

Conversation

@SylvainDe
Copy link
Contributor

Having the same information in two places is quite
painful and proves to lead to a few errors here and
there.
The generate file is not exactly similar to the
README I've commited because there are a few
discrepencies that I do not quite know how to handle
(related to multiple links for slides/other resources)
as I did not dare changing the format of the json file
not to break things.

Having the same information in two places is quite
painful and proves to lead to a few errors here and
there.
The generate file is not exactly similar to the
README I've commited because there are a few
discrepencies that I do not quite know how to handle
(related to multiple links for slides/other resources)
as I did not dare changing the format of the json file
not to break things.
@s16h
Copy link
Owner

s16h commented Jul 26, 2015

AWESOME! Thanks a lot. Will review and merge soon. I have to have a think about how to go about certain things like multiple links or multi-part videos (Part 1, Part 2 etc.). But this is fantastic. Thank you.

@SylvainDe
Copy link
Contributor Author

Glad you like it! Feel free to improve anything :-)
Le 26 juil. 2015 11:33 PM, "Shahriar Tajbakhsh" [email protected]
a écrit :

AWESOME! Thanks a lot. Will review and merge soon. I have to have a think
about how to go about certain things like multiple links or multi-part
videos (Part 1, Part 2 etc.). But this is fantastic. Thank you.


Reply to this email directly or view it on GitHub
#64 (comment).

@SylvainDe
Copy link
Contributor Author

Hi @s16h ,
I just realized that this PR now has merging issues.
How do you want to proceed regarding the changes you had in mind (multiple links, multi-part video) ?
Do you want to take over or should I update my PR so that you can merge it and then you'll change whatever needs to be changed ?

@s16h
Copy link
Owner

s16h commented Oct 25, 2015

Hey @SylvainDe, sorry for the late reply. I've been a bit busy recently but I'm back now :)

I'll go over this and sort it out over the next few days. Thanks again; it's awesome!

@SylvainDe
Copy link
Contributor Author

No problem whatsoever.

Watching your github activity, I knew you had better things to do, I was a bit concerned if you had any personal issues but I'm glad to learn you were just busy and that you are back. Just let me know if you want me to handle merge issues and when (so that I don't do it over and over).

@SylvainDe
Copy link
Contributor Author

Hi @s16h ,
Just a quick message to be sure that you still plan to handle this pull-request (merge conflicts, improvements, etc). Let me know if you need help.

@s16h
Copy link
Owner

s16h commented Nov 29, 2015

I'll be working on it at some point soon. I've been quite busy recently :(

@s16h
Copy link
Owner

s16h commented Jun 22, 2016

Still on my radar...

@SylvainDe
Copy link
Contributor Author

Cool :-)

Le 23 juin 2016 00:08, "Shahriar Tajbakhsh" [email protected] a
écrit :

Still on my radar...


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#64 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABL0rQ34snQJFQzVH416yxYslSos_IC3ks5qObJrgaJpZM4Ff5WE
.

@SylvainDe
Copy link
Contributor Author

Any news ? :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants