A way of creating directory if it doesn't exist? about ncp

[Jonahss]

Ah yes. So your forked repo won't have these fine people's pull requests, since they didn't request YOU for the pull request :)

take a look at this graph: https://github.com/AvianFlu/ncp/network
That's all the people who have forked this repo and added their own changes. I suggest u look through them all (or the list of PRs on this repo), add their repos as remotes, and merge all their changes into one updated version of this repo :)

If you do that successfully, we may be able to petition npm for the rights to this module, since the author seems to have dropped off the map.

[Jonahss]

👍
How about using node-mkdirp for this

[GochoMugo]

👍 really looking forward for this feature. This will allow not requiring to wrap ncp() with fs.mkdir() (or something alike).

[pgangwani]

Yeah, thanks man, I could manage to merge 16 , 26 more to review.

…

On Thu, Feb 16, 2017 at 12:47 AM, Jonah ***@***.***> wrote: I don't quite understand your question. Basically, you should read all the code for this module, evaluate various pull requests, merge the ones you think belong in the module. make sure it works, make sure there is adequate test coverage, then publish a new module that you are happy with. If the module is an improvement on the original, you can suggest a pull request to this repo, or publish on npm under a different name. If you think the community will find your improved version more useful, we can petition npm to take the module name from this outdated repo. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANpzLNAQUgiUJhiOZCY_sxgf4sCWPBj2ks5rc09igaJpZM4Cc_8e> .

[pgangwani]

Hello Guys, I need to get the fix like it asked here, Please help

[Jonahss]

There's so many unmerged pull requests on this repo. maybe it's time for somebody to fork this repo, merge them all, and publish.

[pgangwani]

@AvianFlu @Jonahss : Can you guys please help

[Jonahss]

Well. I can help advise, but I don't have a whole workday to devote to this.
@pgangwani are you a javascript developer?

[pgangwani]

Yes , i am . I couldn't find any PR in the forked branch . May be need some one to review most of important and merge.

…

On 15-Feb-2017 3:30 AM, "Jonah" ***@***.***> wrote: Well. I can help advise, but I don't have a whole workday to devote to this. @pgangwani <https://github.com/pgangwani> are you a javascript developer? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANpzLBvRIF02aBlNmzB4UdlUQAx2F5NDks5rciQJgaJpZM4Cc_8e> .

[Jonahss]

@pgangwani Did you find a solution? Need any help?

[pgangwani]

Unfortunately, I didn't get time, I am adding you as collabrator , Please help there

…

On Wed, Feb 15, 2017 at 9:59 PM, Jonah ***@***.***> wrote: @pgangwani <https://github.com/pgangwani> Did you find a solution? Need any help? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANpzLNwYgm93s5THpzGIJmudMqXc9y4tks5rcyfcgaJpZM4Cc_8e> .

[pgangwani]

@Jonahss : Are you seeing my merges

[Jonahss]

Uh no. can you send me a link to what you're talking about?

[pgangwani]

https://github.com/pgangwani/ncp

…

On Wed, Feb 15, 2017 at 11:48 PM, Jonah ***@***.***> wrote: Uh no. can you send me a link to what you're talking about? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANpzLMtossmmK3mSiluVAEApIyBxfZQGks5rc0FngaJpZM4Cc_8e> .

[Jonahss]

Cool. I would suggest running tests and making sure the code works after merging all those.

[pgangwani]

OK , I am merging so many PRs for first time, can you run whatever I have done till now.

…

On Thu, Feb 16, 2017 at 12:18 AM, Jonah ***@***.***> wrote: Cool. I would suggest running tests and making sure the code works after merging all those. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANpzLB_Xpr-ZhkgxmtwZNDJ9nTRCN4VJks5rc0iGgaJpZM4Cc_8e> .

[pgangwani]

Do I need to configure test somewhere for new PRs On Thu, Feb 16, 2017 at 12:19 AM, pawan gangwani <[email protected]> wrote:

…

OK , I am merging so many PRs for first time, can you run whatever I have done till now. On Thu, Feb 16, 2017 at 12:18 AM, Jonah ***@***.***> wrote: > Cool. I would suggest running tests and making sure the code works after > merging all those. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#54 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ANpzLB_Xpr-ZhkgxmtwZNDJ9nTRCN4VJks5rc0iGgaJpZM4Cc_8e> > . >

[Jonahss]

I don't quite understand your question. Basically, you should read all the code for this module, evaluate various pull requests, merge the ones you think belong in the module. make sure it works, make sure there is adequate test coverage, then publish a new module that you are happy with.

If the module is an improvement on the original, you can suggest a pull request to this repo, or publish on npm under a different name.

If you think the community will find your improved version more useful, we can petition npm to take the module name from this outdated repo.

[Jonahss]

Cool!