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

Re: Cross-Platform Version Control (was: Eric Sink's blog - notes on git, dscms and a "whole product" approach)

From
Jeff King <peff@peff.net>
Date
Apr 29, 2009, 07:21 UTC
Message-ID
<20090429072105.GD22593@coredump.intra.peff.net>
In-Reply-To
<46a038f90904282355g43bf0cv909905f6028f054f@mail.gmail.com>
On Wed, Apr 29, 2009 at 08:55:29AM +0200, Martin Langhoff wrote:
> So from Eric's perspective, it is worthwhile to work on all those
> issues, and get the right for the end user -- support things we don't
> like, offer foolproof catches and warnings that prevent the user from
> shooting their lovely toes off to mars, etc.

I read a few of his blog postings. He kept complaining about the features of git that I like the most. :)

So one thing I took away from it is that there probably isn't _one_ interface that works for everybody. I can see his arguments about how "add -p" can be dangerous, and how history rewriting can be dangerous. So for some users, blocking those features makes sense.

But for other users (myself included), those are critical features that make me _way_ more productive. And I manage the risk that comes from using them as part of my workflow, and it isn't a problem in practice.

While part of me is happy that cogito is now dead (not because I didn't think it was good, but because having two sets of tools just seemed to create maintenance and staleness headaches), I do sometimes wonder if we would be better off with several "from scratch" git interfaces based around the plumbing (or even a C library). And I don't just mean simple wrappers around git commands, but whole new interfaces which make decisions like "no history rewriting at all", and try to provide a safer interface based on that.

Of course, _I_ wouldn't want to use such an interface. But in theory I could seamlessly interoperate with people who did.

-Peff
Previous: Martin LanghoffNext: Markus Heidelberg
Message 5 of 39 in “Eric Sink's blog - notes on git, dscms and a "whole product" approach”
  1. Martin LanghoffApr 27, 2009
  2. Cross-Platform Version Control (was: Eric Sink's blog - notes on git, dscms and a "whole product" approach)Jakub Narebski, Apr 28, 2009
  3. Robin RosenbergApr 28, 2009
  4. Martin LanghoffApr 29, 2009
  5. Jeff KingApr 29, 2009
  6. Markus HeidelbergApr 29, 2009
  7. Jakub NarebskiApr 29, 2009
  8. Martin LanghoffApr 29, 2009
  9. Jakub NarebskiApr 28, 2009
  10. Sitaram ChamartyApr 29, 2009
  11. Why Git is so fast (was: Re: Eric Sink's blog - notes on git, dscms and a "whole product" approach)Jakub Narebski, Apr 30, 2009
  12. Michael WittenApr 30, 2009
  13. Jakub NarebskiApr 30, 2009
  14. Shawn O. PearceApr 30, 2009
  15. Kjetil BarvikApr 30, 2009
  16. Shawn O. PearceApr 30, 2009
  17. Kjetil BarvikApr 30, 2009
  18. Steven NoonanMay 1, 2009
  19. James PickensMay 1, 2009
  20. Kjetil BarvikMay 1, 2009
  21. Mike HommeyMay 1, 2009
  22. Kjetil BarvikMay 1, 2009
  23. Tony FinchMay 1, 2009
  24. Dmitry PotapovMay 1, 2009
  25. Mike HommeyMay 1, 2009
  26. Dmitry PotapovMay 1, 2009
  27. Shawn O. PearceApr 30, 2009
  28. Jeff KingApr 30, 2009
  29. Linus TorvaldsMay 1, 2009
  30. Jeff KingMay 1, 2009
  31. david@lang.hmMay 1, 2009
  32. Nicolas PitreMay 1, 2009
  33. Daniel BarkalowMay 1, 2009
  34. Linus TorvaldsMay 1, 2009
  35. david@lang.hmMay 1, 2009
  36. Nicolas PitreApr 30, 2009
  37. Alex RiesenApr 30, 2009
  38. Andreas EricssonMay 4, 2009
  39. Jakub NarebskiApr 30, 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.