Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #108493 > unrolled thread

Need advice on github

Back to article view | Back to comp.lang.c

Contents

  Need advice on github Peabody <waybackNO584SPAM44@yahoo.com> - 2017-04-25 16:21 -0500
    Re: Need advice on github bartc <bc@freeuk.com> - 2017-04-25 23:00 +0100
      Re: Need advice on github David Brown <david.brown@hesbynett.no> - 2017-04-26 00:32 +0200
        Re: Need advice on github bartc <bc@freeuk.com> - 2017-04-26 00:28 +0100
          Re: Need advice on github Keith Thompson <kst-u@mib.org> - 2017-04-25 16:51 -0700
      Re: Need advice on github Keith Thompson <kst-u@mib.org> - 2017-04-25 15:43 -0700
      Re: Need advice on github GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-04-26 01:40 +0200
    Re: Need advice on github Keith Thompson <kst-u@mib.org> - 2017-04-25 15:28 -0700
    Re: Need advice on github Jorgen Grahn <grahn+nntp@snipabacken.se> - 2017-04-25 23:53 +0000

#108493 — Need advice on github

I'm just an amateur coder, and have no experience with Git or Github.  And 
really, I don't have any need for elaborate versioning protocols.  But I've 
been working on flashing new firmware versions to TI MSP430G processors using 
custom BSL code and an embedded USB-to-serial adapter, and I'd like to make 
what I've developed available to others in the unlikely event that it would 
be of interest to anyone.

I wonder if it would be possible to upload all the files directly to Github 
in my browser, and not install either the Git shell or the desktop GUI.  Does 
anyone know if that's possible?

Also, my stuff includes two Windows console .exe programs, and one VBS 
script.  One of the .exe files is just a small modification to an open source 
TI file (BSLDEMO2) with the added option to invert the DTR line so the 
program will work with modern USB adapters. The other .exe is a program I 
wrote, with assistance from several people here, that is the equivalent of 
BSLDEMO2 for the G2231's primitive custom BSL protocol.  And the VBS file 
just converts any Intel-hex file to a TI-TXT file as required for BSLDEMO2.

Of course the source code for everything will be included, but since I use a 
kinda oddball MSP430 assembler, and a kinda oddball x86 C compiler,  I'd like 
to include the executables for everything so any downloader won't have to 
deal with my choices. These are small .exe's - about 60K each.

But after spending a lot of time on Youtube and Google and even Github, I 
can't find exactly what the situation is with respect to uploading 
executables to Github.  It seems they accepted them for a while, then didn't, 
then did again, and perhaps it involves something called a "release" which 
isn't really explained anywhere that I can find.

Flying Camp Design includes in one of their repositories their own version of 
BSLDEMO2.exe, and it looks like they just included the .exe in the folder 
with the source code and other stuff.  No release that I could find.

So if someone could clarify this for me, I would appreciate it.

[toc] | [next] | [standalone]

#108496

On 25/04/2017 22:21, Peabody wrote:

> But after spending a lot of time on Youtube and Google and even Github, I
> can't find exactly what the situation is with respect to uploading
> executables to Github.  It seems they accepted them for a while, then didn't,
> then did again, and perhaps it involves something called a "release" which
> isn't really explained anywhere that I can find.
>
> Flying Camp Design includes in one of their repositories their own version of
> BSLDEMO2.exe, and it looks like they just included the .exe in the folder
> with the source code and other stuff.  No release that I could find.
>
> So if someone could clarify this for me, I would appreciate it.

I'd quite like some clarification too. I've been informed in this group 
(comp.lang.c) that I wasn't even allowed to upload C source code to 
github. The reason: because my source was translated by a program from 
another language, and thus didn't count as true source code.


-- 
bartc

[toc] | [prev] | [next] | [standalone]

#108499

On 26/04/17 00:00, bartc wrote:
> On 25/04/2017 22:21, Peabody wrote:
>
>> But after spending a lot of time on Youtube and Google and even Github, I
>> can't find exactly what the situation is with respect to uploading
>> executables to Github.  It seems they accepted them for a while, then
>> didn't,
>> then did again, and perhaps it involves something called a "release"
>> which
>> isn't really explained anywhere that I can find.
>>
>> Flying Camp Design includes in one of their repositories their own
>> version of
>> BSLDEMO2.exe, and it looks like they just included the .exe in the folder
>> with the source code and other stuff.  No release that I could find.
>>
>> So if someone could clarify this for me, I would appreciate it.
>
> I'd quite like some clarification too. I've been informed in this group
> (comp.lang.c) that I wasn't even allowed to upload C source code to
> github. The reason: because my source was translated by a program from
> another language, and thus didn't count as true source code.
>

My understanding (which may be wrong) is that it's fine to have binary 
or generated files on Github - but you will also need the source code 
under a suitable open source license.  So if your C files are generated 
as translations from another source language, then you are free to post 
the C files, but you also need to post the original source files.  I 
don't know what the rules are if those original source files are in a 
secret language without readily available translator tools.

[toc] | [prev] | [next] | [standalone]

#108504

On 25/04/2017 23:32, David Brown wrote:
> On 26/04/17 00:00, bartc wrote:
>> On 25/04/2017 22:21, Peabody wrote:

>> I'd quite like some clarification too. I've been informed in this group
>> (comp.lang.c) that I wasn't even allowed to upload C source code to
>> github. The reason: because my source was translated by a program from
>> another language, and thus didn't count as true source code.
>
> My understanding (which may be wrong) is that it's fine to have binary
> or generated files on Github - but you will also need the source code
> under a suitable open source license.  So if your C files are generated
> as translations from another source language, then you are free to post
> the C files, but you also need to post the original source files.  I
> don't know what the rules are if those original source files are in a
> secret language without readily available translator tools.
>
It doesn't need to be a secret language. It could be one for which 
binary tools are not so easy to obtain unless they are supplied with the 
source. A bit like the OP's situation.

So perhaps the answer is to also supply sources to those tools. But 
suppose the tools to process those sources themselves need special 
tools, so we upload sources for those too. And sometimes you end up 
where you started with a circular chain of source dependencies.

But it doesn't matter because, if someone had been thinking of doing a 
download of the original project, by now they would long have given up.

(This is the situation with my projects. Project X is written in A but 
made available as C source. A needs a compiler Y, which is written in B. 
B needs a compiler Z, which is written in A. I'm not making this up.

What would be the case if a C version wasn't viable? Rules like github's 
don't make it easy for those who want to use new, unusual or obscure 
languages.

I guess if github got difficult it would be time to dust off my FTP 
program and use a private website.)

-- 
bartc

[toc] | [prev] | [next] | [standalone]

#108507

bartc <bc@freeuk.com> writes:
[snip]
> What would be the case if a C version wasn't viable? Rules like github's 
> don't make it easy for those who want to use new, unusual or obscure 
> languages.
>
> I guess if github got difficult it would be time to dust off my FTP 
> program and use a private website.)

I believe you are mistaken about GitHub's rules.  I've commented in more
detail by e-mail.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

[toc] | [prev] | [next] | [standalone]

#108501

bartc <bc@freeuk.com> writes:
[...]
> I'd quite like some clarification too. I've been informed in this group 
> (comp.lang.c) that I wasn't even allowed to upload C source code to 
> github. The reason: because my source was translated by a program from 
> another language, and thus didn't count as true source code.

I don't recall anyone here ever telling you that, or anything
resembling it, but I could have missed something.  If there is such
an issue, then it would have to do with GitHub policies, not with C.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

[toc] | [prev] | [next] | [standalone]

#108506

On Tue, 25 Apr 2017 23:00:20 +0100
bartc <bc@freeuk.com> wrote:

> I'd quite like some clarification too. I've been informed in this group 
> (comp.lang.c) that I wasn't even allowed to upload C source code to 
> github. The reason: because my source was translated by a program from 
> another language, and thus didn't count as true source code.

From my understanding, disassembled binaries don't account as open sources to be
hosted in GitHub. More generally, translated files don't account as original
sources.

[toc] | [prev] | [next] | [standalone]

#108498

Peabody <waybackNO584SPAM44@yahoo.com> writes:
> I'm just an amateur coder, and have no experience with Git or Github.
> And really, I don't have any need for elaborate versioning protocols.
> But I've been working on flashing new firmware versions to TI MSP430G
> processors using custom BSL code and an embedded USB-to-serial
> adapter, and I'd like to make what I've developed available to others
> in the unlikely event that it would be of interest to anyone.
[...]

Your question isn't about the C programming language, so this isn't the
place to ask.

I suggest you start at https://help.github.com/

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

[toc] | [prev] | [next] | [standalone]

#108508

On Tue, 2017-04-25, Peabody wrote:
> I'm just an amateur coder, and have no experience with Git or Github.  And 
> really, I don't have any need for elaborate versioning protocols.

You do; you just don't know it yet.  Everyone who produces data would
benefit from version control, for a number of reasons.  (In my
opinion, of course.)

It doesn't have to be elaborate.  You could tell yourself "I will
produce a new version every Sunday morning, and push it to Github" and
that would work.

> But I've 
> been working on flashing new firmware versions to TI MSP430G processors using 
> custom BSL code and an embedded USB-to-serial adapter, and I'd like to make 
> what I've developed available to others in the unlikely event that it would 
> be of interest to anyone.
>
> I wonder if it would be possible to upload all the files directly to Github 
> in my browser, and not install either the Git shell or the desktop GUI.  Does 
> anyone know if that's possible?

I don't know (I treat Github as just another remote Git repository),
but I doubt it. Github is about people sharing data by syncing Git
repositories back and forth.  I doubt that Github has any logic for
modifying a Git repository, which is basically what you're asking for.

[snip]

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c

csiph-web