Transfer of 'jshashtable' npm package name

[timdown]

I'm jshashtable's author. How would you feel about transferring the package name to me? If not, no worries, I'll submit a PR for updating the copy of jshashtable here to version 3.0.

[paulhayes]

Yes, that would be my pleasure. What's your github username?

On Sun, 31 May 2015 13:14 Tim Down [email protected] wrote:

I'm jshashtable's author. How would you feel about transferring the
package name to me? If not, no worries, I'll submit a PR for updating the
copy of jshashtable here to version 3.0.

—
Reply to this email directly or view it on GitHub
#1.

[timdown]

timdown

[paulhayes]

Going to try and do it on my phone now.

On Sun, 31 May 2015 17:36 Tim Down [email protected] wrote:

timdown

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

[timdown]

There's no hurry.

[paulhayes]

Okay, I've set up the transfer request. I think you have to confirm.

Ps You might want to create a bower package for jshashtable.

On Sun, 31 May 2015 17:49 Paul Hayes [email protected] wrote:

Going to try and do it on my phone now.

On Sun, 31 May 2015 17:36 Tim Down [email protected] wrote:

timdown

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

[timdown]

Thanks. I'll do the Bower thing as well.

[timdown]

Ah, I meant the npm package name, not the GitHub project. Sorry for the
confusion. Maybe control of the GitHub project is enough, I'll have to look
into it.

On 31 May 2015 at 17:56, Paul Hayes [email protected] wrote:

Okay, I've set up the transfer request. I think you have to confirm.

Ps You might want to create a bower package for jshashtable.

On Sun, 31 May 2015 17:49 Paul Hayes [email protected] wrote:

Going to try and do it on my phone now.

On Sun, 31 May 2015 17:36 Tim Down [email protected] wrote:

timdown

—
Reply to this email directly or view it on GitHub
<
#1 (comment)

.

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

[paulhayes]

No problem, I'll have to take a look into how to do that on npm.

On Thu, 4 Jun 2015 00:44 Tim Down [email protected] wrote:

Ah, I meant the npm package name, not the GitHub project. Sorry for the
confusion. Maybe control of the GitHub project is enough, I'll have to look
into it.

On 31 May 2015 at 17:56, Paul Hayes [email protected] wrote:

Okay, I've set up the transfer request. I think you have to confirm.

Ps You might want to create a bower package for jshashtable.

On Sun, 31 May 2015 17:49 Paul Hayes [email protected]
wrote:

Going to try and do it on my phone now.

On Sun, 31 May 2015 17:36 Tim Down [email protected] wrote:

timdown

—
Reply to this email directly or view it on GitHub
<

#1 (comment)

.

—
Reply to this email directly or view it on GitHub
<
#1 (comment)

.

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

[paulhayes]

Hi Tim,
I've unpublished js-hashtable on npm. Your free to publish it yourself
now.

On Thu, 4 Jun 2015 at 07:53 Paul Hayes [email protected] wrote:

No problem, I'll have to take a look into how to do that on npm.

On Thu, 4 Jun 2015 00:44 Tim Down [email protected] wrote:

Ah, I meant the npm package name, not the GitHub project. Sorry for the
confusion. Maybe control of the GitHub project is enough, I'll have to
look
into it.

On 31 May 2015 at 17:56, Paul Hayes [email protected] wrote:

Okay, I've set up the transfer request. I think you have to confirm.

Ps You might want to create a bower package for jshashtable.

On Sun, 31 May 2015 17:49 Paul Hayes [email protected]
wrote:

Going to try and do it on my phone now.

On Sun, 31 May 2015 17:36 Tim Down [email protected] wrote:

timdown

—
Reply to this email directly or view it on GitHub
<

#1 (comment)

.

—
Reply to this email directly or view it on GitHub
<
#1 (comment)

.

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