3 ms·

Thanks! I have some open source projects where I only have one LICENSE file (it is also in README), but I will consider adding it to all files, there are just t

Thanks! I have some open source projects where I only have one LICENSE file (it is also in README), but I will consider adding it to all files, there are just too many files. :/ I am inconsistent, because I have projects that contain the copyright notice in all files.

ryao 2y ago
[flagged]
- deleted 2y ago
  [deleted]
- matkoniecz 2y ago
  Why you think that LLM-generated legal advise is worth posting on forum for humans?
  - DrammBA 2y ago
    > Why you think that LLM-generated legal advise is worth posting on forum for humans? Can you quote which part of the LLM chat above constitutes legal advice? I read the whole chat and didn't see any.
    - DrammBA 2y ago
      for reference this was the chat that allegedly contained legal advice: https://chatgpt.com/share/6806382f-7944-800f-95aa-8c770276237e https://chatgpt.com/share/6806382f-7944-800f-95aa-8c77027623...
      - ryao 2y ago
        It does not. It simply discusses ways of adding headers to arbitrary source code. The intention is to add license and copyright headers, but the reality is that these headers can say anything. It is discussing generic techniques for doing this.
  - johnisgood 2y ago
    It is for inserting a copyright notice in the files, I will use a for loop and sed for it though. I'm old school. :P
  - ryao 2y ago
    It is advice for how to add headers to source files, not legal advice. This is a generic concept and the headers could literally say anything. They just happen to be license and copyright notices, since that is what he needs them to be. It is easier than opening each file in a text editor to manually add the header.