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

Re: [PATCH/POLL] git-format-patch: the default suffix is now .patch, not .txt

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jan 18, 2007, 13:40 UTC
Message-ID
<81b0412b0701180540x15d20453s3dbc0c061fd06d50@mail.gmail.com>
In-Reply-To
<625fc13d0701180352m151cceb3lf9c00b6cf0ae937b@mail.gmail.com>
On 1/18/07, Josh Boyer <jwboyer@gmail.com> wrote:
Show 9 quoted lines
> > I think we'd raising the entry barrier with choosing the defaults
> > being so convenient for us. Well, the real-life programmers
> > are less of Unix-liking kind. They are more lazy and demotivated
> > kind, and Git will be _forced_ on them. It almost certainly
> > will not be their choice. Not always, some'll like it (heck, I know
> > people who swear by Perforce!), but most have a job, source
> > of income, and not the profession (like in professional pride).
>
> real-life programmers?  Please don't generalize.  It's insulting.

Just because you are not able to realize that the count of windows-based projects is still superior to that of say... "likable" systems, they wont magically disappear. If that is the case, I think I do some more insulting and say that they are not only real-life but also will never accept the statement of their ways being wrong, however stupid they may appear. That's just how it is, count them if you don't believe me.

Show 7 quoted lines
> > As much as like Unix and everything related, I think it is
> > not reasonable to try to change the majority. Not unless
> > we have something earth-shattering. Well, git is, but
> > 0001-fix....patch in email attachment probably not.
>
> I would venture to say that the _majority_ of git users are not using
> Windows.

The _real_ majority of the programmers desperately need a better VCS than CVS, SVN, Perforce, SourceSafe, ClearCase, etc.

> In this enviroment, Linux is likely the dominant OS,
> followed by other *nix.  So changing the extention to benefit the
> majorit of _git's_ users is a good thing.

Yes. For me and you. One of my coworkers knows nothing about patches, but wants (and perfectly able to) review my code. He has usable brains and is able to figure out what "+" and "-" is (he has, by now). He hasn't even realized that it was an automatically generated information, as I sent a patch to him first time, thought it was just a funny way to document changes (and was surprised when I told him a patch can be applied automatically, even if the original file is not exactly the same). But he is a typical windows-trained programmer. Lazy, unmotivated and happily married. He does programming by accident (was smart enough to learn the basics of the trade). Why would he want to take the an extra step of figuring out what that strange "0001-...patch" means? Now, I know him, would never think about sending him a real patch. I'm kinda grown and tired, and need the bastard, too. Someone younger will just call him idiot and "improve" the situation by telling him about "stupid windows" and "he should the right ways". Just to be answered "it worked for some millions programmers before you" and "I told your manager you making problems and are hard to communicate with".

People often understand "funny ways" the others may have. They don't like been told they are wrong or stupid (especially when they actually are stupid).

Previous: Alex RiesenNext: Andreas Ericsson
Message 32 of 59 in “[RFC] Add a suffix option to git-format-patch”
  1. Josh BoyerJan 17, 2007
  2. Johannes SchindelinJan 17, 2007
  3. Josh BoyerJan 17, 2007
  4. Horst H. von BrandJan 17, 2007
  5. Introduce 'git-format-patch --suffix=patch'Junio C Hamano, Jan 17, 2007
  6. Andy WhitcroftJan 17, 2007
  7. Junio C HamanoJan 17, 2007
  8. Brian GernhardtJan 17, 2007
  9. Junio C HamanoJan 17, 2007
  10. Brian GernhardtJan 17, 2007
  11. Make format-patch --suffix="" not add any suffixBrian Gernhardt, Jan 17, 2007
  12. Johannes SchindelinJan 18, 2007
  13. David KågedalJan 17, 2007
  14. Andreas EricssonJan 17, 2007
  15. Johannes SchindelinJan 17, 2007
  16. Junio C HamanoJan 17, 2007
  17. David KågedalJan 17, 2007
  18. Josh BoyerJan 17, 2007
  19. Josh BoyerJan 17, 2007
  20. git-format-patch: the default suffix is now .patch, not .txtJunio C Hamano, Jan 18, 2007
  21. Johannes SchindelinJan 18, 2007
  22. Alex RiesenJan 18, 2007
  23. Shawn O. PearceJan 18, 2007
  24. Alex RiesenJan 18, 2007
  25. Junio C HamanoJan 18, 2007
  26. Alex RiesenJan 18, 2007
  27. Junio C HamanoJan 18, 2007
  28. Alex RiesenJan 18, 2007
  29. Josh BoyerJan 18, 2007
  30. Johannes SchindelinJan 18, 2007
  31. Alex RiesenJan 18, 2007
  32. Alex RiesenJan 18, 2007
  33. Andreas EricssonJan 18, 2007
  34. Johannes SchindelinJan 18, 2007
  35. Alex RiesenJan 18, 2007
  36. Johannes SchindelinJan 18, 2007
  37. Alex RiesenJan 18, 2007
  38. Johannes SchindelinJan 18, 2007
  39. Alex RiesenJan 18, 2007
  40. Josh BoyerJan 18, 2007
  41. Johannes SchindelinJan 18, 2007
  42. Josh BoyerJan 18, 2007
  43. Shawn O. PearceJan 18, 2007
  44. Alex RiesenJan 18, 2007
  45. Steven GrimmJan 18, 2007
  46. Johannes SchindelinJan 18, 2007
  47. Johannes SixtJan 18, 2007
  48. Jakub NarebskiJan 19, 2007
  49. Shawn O. PearceJan 18, 2007
  50. Alex RiesenJan 18, 2007
  51. Andreas EricssonJan 18, 2007
  52. Shawn O. PearceJan 18, 2007
  53. Andreas EricssonJan 18, 2007
  54. Martin LanghoffJan 18, 2007
  55. Martin LanghoffJan 18, 2007
  56. Andreas EricssonJan 18, 2007
  57. Lukas SandströmJan 18, 2007
  58. Brian GernhardtJan 18, 2007
  59. Alexandre JulliardJan 18, 2007

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.