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

Re: Nobody is THE one making contribution

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Dec 24, 2020, 02:01 UTC
Message-ID
<87r1ngufmf.fsf@evledraar.gmail.com>
In-Reply-To
<5fe36790793ae_2354120839@natae.notmuch>
On Wed, Dec 23 2020, Felipe Contreras wrote:
Show 7 quoted lines
> When I express my dissenting opinion I'm not saying nobody should write
> a patch on top of mine. Of course they can. Anybody can take my code and
> do whatever they want with it (as long as they don't violate the license
> of the project).
>
> What they cannot do is add my Signed-off-by line to code I don't agree
> with.
I don't think that's what Signed-off-by means, per SubmittingPatches:
    To improve tracking of who did what, we ask you to certify that you
    wrote the patch or have the right to pass it on under the same
    license as ours, by "signing off" your patch[...under the DCO:
    https://developercertificate.org/]

So I find this rather unlikely, but let's say I author a patch for git.git and send it to this ML with a Signed-off-by.

If someone else then takes that patch and changes it in a way that I vehemently disagree with and gets Junio to accept it into git.git in its altered form, that altered patch should still carry my Signed-off-by, as well as that of whoever altered it.

Because it's a trailer for maintaining the licensing paper trail. It doesn't mean "Ævar thinks this patch as it stands is a good idea"[1].

"No Discrimination Against Fields of Endeavor" is an integral part of free software & open source. In our case it means that when you contribute code under our COPYING terms someone else might use in a way you don't approve of.

E.g. I'm sure that arms contractors, totalitarian regimes etc. or other entities some might disapprove of are using git in some way.

That non-restriction on fields of endeavor also extends to individual patches licensed under a free software license & the necessity to maintain a paper trail about who their authors are and if they certified them under the DCO.

1. As an aside, I haven't needed involvement from others to later
   realize that an integrated patch of mine with my SOB maybe wasn't
   such a good idea after all :)
Previous: Felipe ContrerasNext: Felipe Contreras
Message 42 of 70 in “mergetool: use resolved conflicts in all the views”
  1. mergetool: use resolved conflicts in all the viewsFelipe Contreras, Dec 16, 2020
  2. Junio C HamanoDec 16, 2020
  3. Seth HouseDec 16, 2020
  4. Junio C HamanoDec 17, 2020
  5. Felipe ContrerasDec 17, 2020
  6. Johannes SixtDec 17, 2020
  7. Felipe ContrerasDec 17, 2020
  8. Johannes SixtDec 17, 2020
  9. Felipe ContrerasDec 18, 2020
  10. Seth HouseDec 17, 2020
  11. Felipe ContrerasDec 17, 2020
  12. Seth HouseDec 17, 2020
  13. Junio C HamanoDec 17, 2020
  14. Felipe ContrerasDec 18, 2020
  15. Felipe ContrerasDec 18, 2020
  16. Seth HouseDec 18, 2020
  17. Felipe ContrerasDec 18, 2020
  18. Seth HouseDec 18, 2020
  19. Felipe ContrerasDec 18, 2020
  20. Seth HouseDec 19, 2020
  21. Felipe ContrerasDec 19, 2020
  22. Junio C HamanoDec 19, 2020
  23. Felipe ContrerasDec 19, 2020
  24. Junio C HamanoDec 19, 2020
  25. Felipe ContrerasDec 19, 2020
  26. Seth HouseDec 21, 2020
  27. Felipe ContrerasDec 21, 2020
  28. Seth HouseDec 21, 2020
  29. Felipe ContrerasDec 21, 2020
  30. David AguilarDec 21, 2020
  31. Code of conduct violation?Felipe Contreras, Dec 21, 2020
  32. Junio C HamanoDec 22, 2020
  33. Felipe ContrerasDec 22, 2020
  34. Pratyush YadavDec 22, 2020
  35. Felipe ContrerasDec 23, 2020
  36. Junio C HamanoDec 23, 2020
  37. Felipe ContrerasDec 23, 2020
  38. Nobody is THE one making contributionJunio C Hamano, Dec 23, 2020
  39. Felipe ContrerasDec 23, 2020
  40. Junio C HamanoDec 23, 2020
  41. Felipe ContrerasDec 24, 2020
  42. Ævar Arnfjörð BjarmasonDec 24, 2020
  43. Felipe ContrerasDec 24, 2020
  44. Ævar Arnfjörð BjarmasonDec 24, 2020
  45. Felipe ContrerasDec 24, 2020
  46. Junio C HamanoDec 24, 2020
  47. Felipe ContrerasDec 27, 2020
  48. Junio C HamanoDec 27, 2020
  49. Felipe ContrerasDec 27, 2020
  50. Junio C HamanoDec 28, 2020
  51. Felipe ContrerasDec 28, 2020
  52. Randall S. BeckerDec 24, 2020
  53. Felipe ContrerasDec 24, 2020
  54. Junio C HamanoDec 24, 2020
  55. David AguilarDec 24, 2020
  56. Felipe ContrerasDec 24, 2020
  57. Junio C HamanoDec 18, 2020
  58. Felipe ContrerasDec 18, 2020
  59. Junio C HamanoDec 19, 2020
  60. Felipe ContrerasDec 19, 2020
  61. David AguilarDec 20, 2020
  62. Felipe ContrerasDec 20, 2020
  63. David AguilarDec 20, 2020
  64. Felipe ContrerasDec 21, 2020
  65. Seth HouseDec 19, 2020
  66. Felipe ContrerasDec 16, 2020
  67. Junio C HamanoDec 17, 2020
  68. Felipe ContrerasDec 17, 2020
  69. mergetool: use resolved conflicts in all the viewsFelipe Contreras, Dec 17, 2020
  70. Felipe ContrerasDec 21, 2020

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.