Re:Github's fork queue is dangerous
by swombat on Saturday May 16, 2009 @07:19AM
(#612086)
Git tends to "just work". Don't worry.
[ Parent
| on HN ]
They're talking about 'rewriting history'. In a version control system. That's more than a bit scary...
... but apparently I'm the only one who thinks so?! Come on. Git has some neat stuff, but it's not that hard to mess up your repository. And that's a bad thing for a tool that should be either helping or staying out of the way.
Re:Github's fork queue is dangerous
by FooBarWidget on Sunday May 17, 2009 @08:26AM
(#613329)
I don't see how it's rewriting history. Neither cherry-pick nor Fork Queue changes history that has already been published.
That said, rewriting the history of changes before they've been published is a really useful feature. I use it all the time for merging local branches before I publish them.