The normal flow in other technologies:<div><br></div><div>1- Fork the central Cuis repo</div><div>2- Make the changes in your fork</div><div>3- Send a pull request to central Cuis repo</div><div><br></div><div>But you can still keep your repo, and organize it at your wil. And when sure, do the above steps.</div>
<div><br></div><div><br></div><div><div class="gmail_quote">On Sun, Dec 30, 2012 at 10:41 AM, Germán Arduino <span dir="ltr"><<a href="mailto:garduino@gmail.com" target="_blank">garduino@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">ok, but how will we do the switch?<div><br></div><div>I mean, we need to rename all the packages in our local repos? and then commit then to GitHub.... and then delete the old names in GitHub?</div>
<div><br></div><div>We will wait you release fixes in Cuis to consider the new names?</div><div class="HOEnZb"><div class="h5">
<div><br></div><div><br><br><div class="gmail_quote">2012/12/30 Juan Vuletich <span dir="ltr"><<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Angel,<br>
<br>
Yes. From all that, it seems that the way to do it would be to use *.<a href="http://cs.st" target="_blank">cs.st</a> and *.<a href="http://pck.st" target="_blank">pck.st</a> file extensions for ChangeSets and Packages. *.st is the only file extension recognized as Smalltalk. It is a reasonable solution. I thought that a manual override should be possible...<br>
<br>
If we don't find another solution, maybe I'll switch to *.<a href="http://cs.st" target="_blank">cs.st</a> and *.<a href="http://pck.st" target="_blank">pck.st</a> as the defaults in the code, and rename files in the Cuis repository. Then, it would be good if folks start renaming .pck files in their own repository. I guess supporting the older (current!) extensions will not be a problem.<br>
<br>
Cheers,<br>
Juan Vuletich<br>
<br>
Angel Java Lopez wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
I just found:<br>
<br>
<a href="http://stackoverflow.com/questions/5318580/how-does-github-figure-out-a-projects-language" target="_blank">http://stackoverflow.com/<u></u>questions/5318580/how-does-<u></u>github-figure-out-a-projects-<u></u>language</a><br>
<br>
then<br>
<br>
<a href="https://github.com/github/linguist" target="_blank">https://github.com/github/<u></u>linguist</a><br>
<br>
but I don't sure if it is used to classify a project. Is it used beyond syntax highlighting?<br>
<br>
<br>
Language detection<br>
<br></div>
Linguist defines the list of all languages known to GitHub in a yaml file <<a href="https://github.com/github/linguist/blob/master/lib/linguist/languages.yml" target="_blank">https://github.com/github/<u></u>linguist/blob/master/lib/<u></u>linguist/languages.yml</a>>. In order for a file to be highlighted, a language and lexer must be defined there.<div>
<br>
<br>
Most languages are detected by their file extension. This is the fastest and most common situation.<br>
<br></div>
For disambiguating between files with common extensions, we use a bayesian classifier <<a href="https://github.com/github/linguist/blob/master/lib/linguist/classifier.rb" target="_blank">https://github.com/github/<u></u>linguist/blob/master/lib/<u></u>linguist/classifier.rb</a>>. For an example, this helps us tell the difference between |.h| files which could be either C, C++, or Obj-C.<div>
<br>
<br>
<br>
and its issues:<br>
<a href="https://github.com/github/linguist/issues" target="_blank">https://github.com/github/<u></u>linguist/issues</a><br>
<br>
<br>
<br></div><div>
On Sun, Dec 30, 2012 at 9:53 AM, Juan Vuletich <<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a> <mailto:<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>>> wrote:<br>
<br>
Hi Hannes,<br>
<br>
In addition to .pck we also have .cs files. I'd like to be able to<br>
tell GitHub that:<br>
*.pck is Smalltalk<br>
*.cs is Smalltalk<br>
The whole project is a Smalltalk project (so it shows in<br>
<a href="https://github.com/languages/Smalltalk" target="_blank">https://github.com/languages/<u></u>Smalltalk</a> )<br>
<br>
I found how to tell git that some files are in a specific language<br>
(see <a href="http://schacon.github.com/git/gitattributes.html" target="_blank">http://schacon.github.com/git/<u></u>gitattributes.html</a> ), but<br>
smalltalk is not listed there. But if git already thinks that *.st<br>
means smalltalk, I believe the same could be done for *.pck and *.cs.<br>
<br>
Please folks, help me! I can't find a way to do it, but it should<br>
be possible!<br>
<br></div>
As a last resource, we could switch to *.<a href="http://pck.st" target="_blank">pck.st</a> <<a href="http://pck.st" target="_blank">http://pck.st</a>><br>
and *.<a href="http://cs.st" target="_blank">cs.st</a> <<a href="http://cs.st" target="_blank">http://cs.st</a>>, but that would make things a bit more<div><br>
awkward for us, and especially for users of other Smalltalk<br>
environments...<br>
<br>
Thanks,<br>
Juan Vuletich<br>
<br>
H. Hirzel wrote:<br>
<br>
And the packages files (*.pck) should have a Smalltalk<br>
extension *.st,<br></div>
so e.g. *.<a href="http://pck.st" target="_blank">pck.st</a> <<a href="http://pck.st" target="_blank">http://pck.st</a>> so that the repos show up on<div><br>
the github Smalltalk<br>
page.<br>
<br>
<a href="https://github.com/languages/Smalltalk" target="_blank">https://github.com/languages/<u></u>Smalltalk</a><br>
<br>
This makes it easier to see what is going on.<br>
<br>
For example Bernhard's Cuis fork appears there (no *.cs files)<br>
whereas<br>
Juan's does not (many *.cs files, counted as C-Sharp).<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Cuis mailing list<br></div>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a> <mailto:<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a>><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a><br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>------------<div><br>
<br>
______________________________<u></u>_________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a><br>
<br>
</div></blockquote><div><div>
<br>
<br>
______________________________<u></u>_________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div><br></div>
</div></div><br>_______________________________________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a><br>
<br></blockquote></div><br></div>