Skip to content

Correct ".NET" usage #1046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 13, 2015
Merged

Correct ".NET" usage #1046

merged 1 commit into from
May 13, 2015

Conversation

richlander
Copy link
Contributor

  • ".Net" -> ".NET".
  • Make fully upper-case, which is the correct usage.

Note: Would be great if a project owner could make the same change in the repo description. PRs cannot affect that.

- ".Net" -> ".NET".
- Make fully upper-case, which is the correct usage.
@ethomson
Copy link
Member

While we're talking description: are .NET and Mono distinct? Should this not just be "to .NET"?

@nulltoken
Copy link
Member

While we're talking description: are .NET and Mono distinct? Should this not just be "to .NET"?

/cc @Therzok ?

@nulltoken
Copy link
Member

@richlander Thanks!

Repository description has been updated.

@Therzok
Copy link
Member

Therzok commented May 12, 2015

@nulltoken It's actually dependent on what you're trying to say. If you're trying to mention a runtime, then it's Mono/CoreCLR/CLR. If you're trying to mention the .NET stack, it's .NET.

@nulltoken
Copy link
Member

@Therzok Hmmm... So, what would be a correct wording to express that the library is compatible with both the Mono project and Microsoft implementations of the runtime?

/cc @ethomson @richlander

@richlander
Copy link
Contributor Author

I suggest removing Mono from the repo description at the top, just to make it simpler. it's really a statement about this project being the language bindings for .NET at large.

It is important to be clear about .NET and Mono in the readme, since that describes a particular usage scenario.

@migueldeicaza is free to overrule me.

@migueldeicaza
Copy link

Isn't .NET a Microsoft trademark for a particular implementation?

Perhaps a task for the .NET foundation to bless various VMs implementing some/parts of the spec as being .NET or not?

But in the meantime, I do not think it hurts to put both Mono and .NET there.

@richlander
Copy link
Contributor Author

Works for me!

nulltoken added a commit that referenced this pull request May 13, 2015
@nulltoken nulltoken merged commit e1e5fe6 into libgit2:vNext May 13, 2015
@nulltoken
Copy link
Member

Perhaps a task for the .NET foundation to bless various VMs implementing some/parts of the spec as being .NET or not?

/cc @martinwoodward

Meanwhile, let's merge this in.

Cheers!

@nulltoken nulltoken added this to the v0.22 milestone May 13, 2015
@richlander richlander deleted the patch-1 branch May 13, 2015 14:14
@martinwoodward
Copy link
Member

Thanks for the CC - I'll add certification to my list of things to look into.

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.

6 participants