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

Re: [PATCH] Make "git reset" a builtin. (incomplete)

From
Nicolas Pitre <nico@cam.org>
Date
Aug 23, 2007, 15:19 UTC
Message-ID
<alpine.LFD.0.999.0708231110280.16727@xanadu.home>
In-Reply-To
<Pine.LNX.4.64.0708231051210.20400@racer.site>
On Thu, 23 Aug 2007, Johannes Schindelin wrote:
Show 18 quoted lines
> Hi,
> 
> On Wed, 22 Aug 2007, Nicolas Pitre wrote:
> 
> > On Wed, 22 Aug 2007, Johannes Schindelin wrote:
> > 
> > > What is wrong with going from shell to C?  C _is_ portable.  Instead 
> > > of relying on _yet_ another scripting language, introducing _yet_ 
> > > another language that people have to learn to hack git, introducing 
> > > _yet_ another place for bugs to hide, why not just admit that shell is 
> > > nice for _prototyping_?
> > 
> > This is a narrow view of the programming world that I don't share.
> 
> Well, you have to admit that some things are really, really hard to do in 
> shell.  Just from the top of my head: locking, data structures, 
> portability, scalability, process control.  There are a lot more, I guess, 
> but for the _core_ of Git I really prefer C.
I don't dispute that.

I'm more concerned about easy scripting of Git operations that can be shared across different environments.

> I do not want to shove C down the throat of every Git user.  You can use 
> _whatever_ scripting language you like.

Sure. I was thinking that a common scripting language, shipped with Git itself that would work out of the box either on Linux or Windows, could benefit the whole Git user base, with a possible side effect of being able to also run the test suite everywhere. If that has no sufficient merits to other people and only remains a peep dream of mine then so be it.

Nicolas
Previous: Johannes SchindelinNext: Reece Dunn
Message 39 of 49 in “Make "git reset" a builtin. (incomplete)”
  1. Make "git reset" a builtin. (incomplete)Carlos Rica, Aug 22, 2007
  2. David KastrupAug 22, 2007
  3. Andreas EricssonAug 22, 2007
  4. David KastrupAug 22, 2007
  5. Mike HommeyAug 22, 2007
  6. Chris ShoemakerAug 22, 2007
  7. David KastrupAug 22, 2007
  8. Nicolas PitreAug 22, 2007
  9. Johannes SchindelinAug 22, 2007
  10. David KastrupAug 22, 2007
  11. Linus TorvaldsAug 22, 2007
  12. David KastrupAug 22, 2007
  13. Linus TorvaldsAug 22, 2007
  14. David KastrupAug 22, 2007
  15. Linus TorvaldsAug 22, 2007
  16. David KastrupAug 22, 2007
  17. Linus TorvaldsAug 23, 2007
  18. Wincent ColaiutaAug 23, 2007
  19. Nicolas PitreAug 23, 2007
  20. Jon SmirlAug 23, 2007
  21. Linus TorvaldsAug 23, 2007
  22. Junio C HamanoAug 23, 2007
  23. Johannes SchindelinAug 23, 2007
  24. Reece DunnAug 22, 2007
  25. Johannes SchindelinAug 23, 2007
  26. Theodore TsoAug 23, 2007
  27. Johannes SchindelinAug 23, 2007
  28. David TweedAug 23, 2007
  29. Theodore TsoAug 23, 2007
  30. Johannes SchindelinAug 23, 2007
  31. Jon SmirlAug 23, 2007
  32. Reece DunnAug 23, 2007
  33. Alex RiesenAug 23, 2007
  34. David KastrupAug 23, 2007
  35. Alex RiesenAug 23, 2007
  36. David KastrupAug 23, 2007
  37. Nicolas PitreAug 22, 2007
  38. Johannes SchindelinAug 23, 2007
  39. Nicolas PitreAug 23, 2007
  40. Reece DunnAug 22, 2007
  41. Johannes SchindelinAug 23, 2007
  42. Robin RosenbergAug 23, 2007
  43. Nguyen Thai Ngoc DuyAug 23, 2007
  44. Matthieu MoyAug 22, 2007
  45. David KastrupAug 22, 2007
  46. Andy ParkinsAug 22, 2007
  47. Johannes SixtAug 22, 2007
  48. Alex RiesenAug 22, 2007
  49. Johannes SchindelinAug 23, 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.