Git!
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
Allow me to bring my modest contribution. (CEF build excerpt) $ git svn find-rev r251746 _ Oh, I forgot to say: this was started 2 hours ago. Thanks, I have my Ctrl/C.
-
Powerful tool. With power comes responsibility.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Sure. Let's drive a Panzer VI instead of a car. More power, more responsibility. Heil Git.
-
Never tried it. No plans to try it. Using TFS at work and at least it's a step up from Subversion.
You'll never get very far if all you do is follow instructions.
Er, no.
Regards, Rob Philpott.
-
I could say the same thing about a pneumatic drill, but it doesn't mean I want to use one!
No, but if you do, you'd better understand how it works... Decentralised configuration management systems are not trivial (centralised neither, but state-of-the-art now). Plus if you do not need the decentralized way, you may use it as a plain normal centralized version as well.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
-
Sure. Let's drive a Panzer VI instead of a car. More power, more responsibility. Heil Git.
But can it get from Berlin to Warsaw on one tank of fuel?
You'll never get very far if all you do is follow instructions.
-
MarkTJohnson wrote:
We have kind of abandoned branching because it looks and feels like stuff vanishes.
:omg: Branching is the cornerstone of Git (and actually any VCS.) If you don't understand the minimum of how to create, switch, pull and push branches in Git, you shouldn't be using Git. Even with SVN, it's standard to create "dev, test, and prod" branches at a minimum. I'd strongly suggest that your team takes a step back and figures out at least that much of the basics of Git. Marc
Well, they want back to the first feature of source control : backup ! I definitely need to write that article about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
Most useful post I've read today. I was under the impression that GIT cured all source control ills, and I was some sort of luddite for not knowing anything about it. Now I know everyone despises it I will let it bother me no more.
Regards, Rob Philpott.
-
Most useful post I've read today. I was under the impression that GIT cured all source control ills, and I was some sort of luddite for not knowing anything about it. Now I know everyone despises it I will let it bother me no more.
Regards, Rob Philpott.
Chalk up one for not despising it here. I've been using it for the past few months and there's definitely a fairly steep learning curve if you've never used a DVCS before. It certainly has some quirks and annoyances, but as I get used to things I see the benefits. I think the key is finding a workflow that works for what you're doing. I generally use SourceTree as a GUI, which is pretty good, and fall back to the command line when doing some things that aren't supported (interactive rebase being the primary one)
-
We have kind of abandoned branching because it looks and feels like stuff vanishes. Programmers work with files not directory structures, Linus.
Hear hear!
You'll never get very far if all you do is follow instructions.
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
Personally I have little issue with Git. But I just knew that someone would come along and tell everybody the difficulty was their own fault. How nauseatingly immature that is, and how self-destructive. Trying to defend, blindly, a piece of software against a chorus of criticism, developer criticism at that, shows total disregard for the end user and I for one would never show any interest in adopting products created by people like that. Did I already mention I have no problem with Git?
-
Never tried it. No plans to try it. Using TFS at work and at least it's a step up from Subversion.
You'll never get very far if all you do is follow instructions.
I cannot agree with that. I've been using TFS for the past 6 mths, and while I found it to be great Application Development Lifecycle tool, when it comes to the source control, SVN is far superior IMHO. Initially I thought it is just a matter of getting used to the tool and I should give it a chance. After months of experience, I still reckon that common things like branching, merging, blaming, comparing revisions (changesets) or even committing is simpler and more intuitive in SVN.
-
MarkTJohnson wrote:
I could lock the file I was working on and know my changes would go in. If someone had a file I needed locked
Ew. I hated locking files. I thought it was a huge improvement to work with something like SVN that didn't require file locking, and was one of the reasons I never adopted TFS because in its early days, it required file locking. Inevitably, someone would leave a file locked at the end of the day and was nowhere to be found. Marc
Not to mention locking a whole bunch of files, and then leaving the company! I really disliked PVCS... almost as much as CMS on the VAX.
Cheers, Mike Fidler
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
We are moving to Git where I work and this thread is not giving me any warm fuzzies.
-
I totally agree. I REALLY don't understand how it has become so darn popular. It's unintuitive, user-unfriendly and even buggy... :mad: Note: If you pronounce it in French, the name couldn't be more appropriate! :doh: But because it's the hottest thing since Salma Hayek, management insists that we used it. No thanks, give me back SVN - it was easy and nice to work with, and no bugs (that I know of)
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the timeIt is popular because the database follows you around so you can work from home, and on site without connecting back to base. You can check in stuff whenever and wherever. At the end of the day, you still have to merge it with the "master" even though there is no official "master". Yes - I like SVN and I'm sticking to it. I just get a mini-repository when I go off site.
-
It is popular because the database follows you around so you can work from home, and on site without connecting back to base. You can check in stuff whenever and wherever. At the end of the day, you still have to merge it with the "master" even though there is no official "master". Yes - I like SVN and I'm sticking to it. I just get a mini-repository when I go off site.
-
Trust me, if I didn't have to use it I wouldn't. PVCS was wonderful. I could lock the file I was working on and know my changes would go in. If someone had a file I needed locked then I knew I could work on some other item in my queue but we wouldn't be stepping on each other's code.
MarkTJohnson wrote:
I could lock the file I was working on and know my changes would go in. If someone had a file I needed locked then I knew I could work on some other item in my queue but we wouldn't be stepping on each other's code.
If you have that problem except very rarely then it isn't a problem with the source control system. It is a problem with the design, implementation and/or the way tasks are allocated.
-
Branching is evil and should be avoided. It's a sign of a flawed process.
You'll never get very far if all you do is follow instructions.
PIEBALDconsult wrote:
Branching is evil and should be avoided. It's a sign of a flawed process.
The fact that you don't like it and that you claim that you deliver perfect code into production doesn't mean that the rest of the world doesn't need it nor that they shouldn't have it.
-
PIEBALDconsult wrote:
Branching is evil and should be avoided. It's a sign of a flawed process.
Why? I'm on the fence (having seen the usefulness of it in Git), but want to know your reasons. Marc
-
Well, they want back to the first feature of source control : backup ! I definitely need to write that article about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
-
No, but if you do, you'd better understand how it works... Decentralised configuration management systems are not trivial (centralised neither, but state-of-the-art now). Plus if you do not need the decentralized way, you may use it as a plain normal centralized version as well.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Rage wrote:
Decentralised configuration management systems...
Presumably that was a misstatement.
Rage wrote:
Plus if you do not need the decentralized way, you may use it as a plain normal centralized version as well.
Doesn't alter the fact that is missing a primary feature for anything above a small company - that of management of multiple products where there are non-trivial code dependencies between them.