git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Cast things properly to handle >2G files.

From
Alfred M. Szmidt <ams@gnu.org>
Date
Jun 17, 2009, 22:27 UTC
Message-ID
<E1MH3bD-0004g2-97@fencepost.gnu.org>
In-Reply-To
<alpine.LFD.2.01.0906142118250.3305@localhost.localdomain>
   > I cannot agree to the D-C-O in good faith, since it speaks of
   > open source licenses, a group of licenses that include non-free
   > software licenses, something which I cannot support.
   If you can't sign off on it, then Junio shouldn't take it, since
   you're basically saying that you cannot say that you own the
   copyrights or cannot license it under the appropriate copyright.

That is not what I am saying. In either case, I already explained why I cannot agree to the DCO above. And you are right, Junio shouldn't apply the patch if it goes against commit policies.

   Yes, it speaks of "open source licenses", but it says: "under the
   open source license indicated in the file", and "appropriate open
   source license".

That is a good point, almost none of the files in git specify the license so it is impossible to know what one is actually agreeing too.

I would suggest the following update to the DCO, it makes it more general both to free software hackers, and open source hackers alike.

  Developer's Certificate of Origin 1.2-draft
  By making a contribution to this project, I certify that:
  (a) The contribution was created in whole or in part by me and I
      have the right to submit it under the license indicated in the
      file; or
  (b) The contribution is based upon previous work that, to the best
      of my knowledge, is covered under an compatible license and I
      have the right under that license to submit that work with
      modifications, whether created in whole or in part by me, under
      the same license (unless I am permitted to submit under a
      different license), as indicated in the file; or
  (c) The contribution was provided directly to me by some other
      person who certified (a), (b) or (c) and I have not modified it.
  (d) I understand and agree that this project and the contribution
      are public and that a record of the contribution (including all
      personal information I submit with it, including my sign-off) is
      maintained indefinitely and may be redistributed consistent with
      this project or the license(s) involved.
Previous: Linus TorvaldsNext: Linus Torvalds
Message 10 of 23 in “Cast things properly to handle >2G files.”
  1. Cast things properly to handle >2G files.Alfred M. Szmidt, Jun 14, 2009
  2. Johannes SchindelinJun 14, 2009
  3. Nicolas PitreJun 15, 2009
  4. Alfred M. SzmidtJun 15, 2009
  5. Junio C HamanoJun 15, 2009
  6. Johannes SchindelinJun 15, 2009
  7. Linus TorvaldsJun 15, 2009
  8. Alfred M. SzmidtJun 17, 2009
  9. Linus TorvaldsJun 17, 2009
  10. Alfred M. SzmidtJun 17, 2009
  11. Linus TorvaldsJun 17, 2009
  12. Junio C HamanoJun 17, 2009
  13. Fix big left-shifts of unsigned charLinus Torvalds, Jun 18, 2009
  14. Johannes SchindelinJun 18, 2009
  15. Junio C HamanoJun 18, 2009
  16. Linus TorvaldsJun 18, 2009
  17. Johannes SchindelinJun 18, 2009
  18. Linus TorvaldsJun 18, 2009
  19. Fix various sparse warnings in the git source codeLinus Torvalds, Jun 18, 2009
  20. Matthieu MoyJun 18, 2009
  21. Linus TorvaldsJun 18, 2009
  22. Linus TorvaldsJun 18, 2009
  23. Linus TorvaldsJun 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.