develop7

8 ms·

61.
by develop7 12y ago
despite Go isn't actually an answer, good for him anyway
62.
by develop7 12y ago
Everything is better with Bluetoo…^W Git
63.
by develop7 12y ago
well it could be named git-unfuck (1)
64.
by develop7 12y ago
It does rely on history? Well, it won't work for me then — in my history there's only frequently-used commands.
65.
by develop7 12y ago
Soon in Mercurial. Years later (probably never) in Git.
66.
by develop7 13y ago
> to be able to go back to a previous state whenever I need to as I've said, old commits are backed up. > This works great with Git's reflog. except git reflog is cleaned on git gc Not mentioning http://mercur
67.
by develop7 13y ago
Your rebase-based workflow is easily achievable with Mercurial. And there's even --outgoing switch in histedit. > Histedit extension which is meant to provide this feature has warnings all over the place Ignore them — you do know,
68.
by develop7 13y ago
> Overwhelming at times? Absolutely. "At times"? Well, maybe, if you have plenty of time, no paid work to do and no deadline approaching.
69.
by develop7 13y ago
> Google stuff as you go. Are you implying git man pages are useless to newcomer?
70.
by develop7 13y ago
Yup, instead of pushing git core devs into adopting at least mercurial "phases" concept or thinking on another way to solve this problem, reposting "do not handle it this way" guidelines is preferred.
71.
by develop7 13y ago
> _the missing piece that keeps this from being useful is that they can't keep their fork up to date using github.com_ yep, a year ago removed "Fork Queue" would come in handy there.
72.
by develop7 13y ago
Why exactly should I learn how git works? Other DVCS (yes, they do exist!) do not require me to learn their guts to be used effectively — only read man pages. Which, in case of git, are "one big almighty “fuck you”" (© Steve Benne
73.
by develop7 13y ago
I'm pretty much aware of semantic model of distributed version control. Problem is git introduces new concepts (useless outside of git) which are widely used with and without cause. Check out various short descriptions of push command:
74.
by develop7 13y ago
Of course, all they had to read and follow was "contributing to sqlalchemy" manual.
75.
by develop7 13y ago
> you weren't properly taught how git actually works I'm using git (well, forced to, in fact) since 2009 and I've learned its' guts. And I still can't see why should I care of .git contents unless I'm git developer. Ask yourself this: h
76.
by develop7 13y ago
1. What a huge saving — 0,002¢ per repo copy. Don't spend it all in one place. 2. Bookmarks is core feature since March 2011. This basically means those who pushed "move to Git" decision, haven't checked if anything was updated in Mercurial
77.
by develop7 13y ago
Well, git sucks a lot, but switch to CVCS instead? No way.
78.
by develop7 13y ago
No, git doesn't track renames — git _guesses_ them
79.
by develop7 13y ago
Create a pull request to https://bitbucket.org/sjl/stevelosh
80.
by develop7 13y ago
> git is only used by expert users 1 235 026 expert users, my eye
81.
by develop7 14y ago
It's v27.something-dev.
82.
by develop7 14y ago
well, in fact they do support it — there's Widevine plugin in chrome://plugins/ (/opt/google/chrome/libwidevinecdmadapter.so)
83.
by develop7 14y ago
> The patterns in .gitignore and .gitattributes files can have /, as a pattern that matches 0 or more levels of subdirectory. Mercurial had this for ages.
84.
by develop7 14y ago
is there a complete list of ways I should avoid to hold git?
85.
by develop7 14y ago
"avoid holding it that way"?
86.
by develop7 15y ago
You're doing everything wrong. Literally everything.