Re: [tsc-devel] Repository has been renamed

Quintus | Fri, 03 Oct 2014 17:29:15 UTC

Hi Brian,

Brian Allen Vanderburg II <…2@a…> writes:
>  I had some
> problems fetching with the origin you specified (something about public
> key issue), so I just used https://github.com/Secretchonicles/TSC.git
> and it seems to be working.

You can also use the HTTPS URL of course. The remote URL I posted was an
SSH one, as I was under the impression that SSH was the normal way to
push to Git repositories; GitHub has supported pushing over SSH much
longer than pushing over HTTPS. In the end it does not matter which way
you choose to push to the repository, use whatever you are fine with.

> I imagine later we will eventually update the source code namespace for
> both C++ and scripting and the binary to be called tsc or something
> like that?

Of course. The main namespace has to be renamed from “SMC” to “TSC”, and
the occurences of “Maryo” and similar have to be removed. The executable
has to be renamed as well (editing CMakeLists.txt). datahead had some
concerns against doing so if I remember; datahead, would you be so kind
and repeat them?

In any case, when renaming is due, it should be done on the release
branch first, which will then get merged into the devel branch. I
remember the merging nightmare on the coding style changes too good as
to do the same mistake again.

On that matter, we have some really old naming in our
sourcecode. There’s still “jPiranha” for example in the Flyon code. This
has also to be removed sometime.

> Thanks,
>
> Brian Allen Vanderburg II

Vale,
Quintus

-- 
Blog: http://www.quintilianus.eu

I will reject HTML emails.     | Ich akzeptiere keine HTML-Nachrichten.
                               |
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung:
http://www.gnupg.org           | http://gnupg.org/index.de.html