Timeline for Is there tool agnostic terminology for source control activities?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2012 at 16:05 | comment | added | Minthos | I should get a badge for provoking so many good and thoughtful responses with my unpopular answer :) | |
| Dec 7, 2012 at 12:23 | comment | added | Bryan Oakley | Gold standard? It's popular, but not a gold standard. | |
| Dec 7, 2012 at 11:57 | comment | added | jammycakes | Given that, among other things, what Git calls a "branch" isn't actually a branch (it's more akin to what anyone with any sense would call a tag, a label or a bookmark), and that a "fast forward merge" doesn't actually merge anything, Git is not exactly a shining example in terms of terminology. | |
| Dec 6, 2012 at 22:04 | comment | added | Kaz | The git command line utilities are for complete masochists. You have to understand the semantics of the git implementation to use it effectively, and to know how to respond in every scenario. And it doesn't even handle renaming (directory structure versioning). | |
| Dec 6, 2012 at 16:51 | comment | added | Lazy Badger | Gitboys... Oh, God, no, please!!! Except fact of unwanted ads here, Git actively refuse to use conventional revision control terminology. "Sorry, you use checkout to revert a commit? And checkout also switches between branches? revert is like a merge? WTF?" (c) André Pang | |
| Dec 6, 2012 at 16:37 | comment | added | Minthos | Fair enough. I'll leave my question up to collect downvotes, because I still think my answer is correct. | |
| Dec 6, 2012 at 16:25 | comment | added | C. Ross | @Minthos The point is to be able to discuss all the available tools and the process in a way that the team can all understand. Shilling for Git doesn't help that in any way. | |
| Dec 6, 2012 at 16:16 | history | edited | Minthos | CC BY-SA 3.0 | added 291 characters in body |
| Dec 6, 2012 at 16:11 | comment | added | Minthos | In that case they should learn about Git, understand why it's so highly regarded, and compare their alternatives to it. It's a very instructive activity that will give them the perspective they need to make a good decision. | |
| Dec 6, 2012 at 16:02 | comment | added | Walter | This really doesn't answer the question. While the tool may be popular, the question was for terminology that was not tool specific. What happens if no one on his team has ever seen or used Git? | |
| Dec 6, 2012 at 15:56 | review | First posts | |||
| Dec 6, 2012 at 15:57 | |||||
| Dec 6, 2012 at 15:36 | history | answered | Minthos | CC BY-SA 3.0 |