|
samiamwork posted:Wow, Google Code has had Mercurial support since the end of April: They ripped out Mercurial's native storage implementation and made it a wrapper around BigTable, which isn't something you can easily do with git.
|
#
¿
Sep 15, 2009 00:43
|
|
|
|
| # ¿ May 3, 2024 21:12 |
|
|
Apparently y'all misunderstood the purpose of rebasing. It isn't intended to avoid merges, it's intended to avoid excessive merges. i.e. it is the difference between this: code:code:pseudorandom name fucked around with this message at 19:56 on Aug 18, 2010 |
|
#
¿
Aug 18, 2010 19:49
|
|
|
There's nothing scary about fast-forward merges, it's just the simple observation that when you merge A <- B <- C <- D <- E into A <- B <- C, you don't actually have to do any work.
|
|
#
¿
Jan 19, 2011 07:17
|
|
|
Wouldn't it make more sense to have a single branch and different targets in your build system that output the free and paid versions?
|
|
#
¿
Mar 24, 2011 01:40
|
|
|
ISTR something about github's implementation of git being a rewrite from scratch in Erlang or some other functional language.
|
|
#
¿
Aug 20, 2011 05:27
|
|
|
I like git gui more than git add -p.
|
|
#
¿
Sep 4, 2011 20:01
|
|
|
Abusing git's diff hunk header generation to figuring which functions were changed is a terrible idea, simply because git has no knowledge of the source language's syntax.
|
|
#
¿
Oct 1, 2011 00:53
|
|
|
OAuth keys aren't like DVD CSS keys, they can be easily revoked and replaced with no real impact on anybody at all. And nobody really bothers to reverse engineer binaries for them, because they just aren't that interesting to begin with.
|
|
#
¿
Oct 5, 2011 01:06
|
|
|
Rebase creates new commits, complete with new timestamps.
|
|
#
¿
Oct 8, 2011 01:32
|
|
|
git push also has a --delete option.
|
|
#
¿
Dec 1, 2011 18:48
|
|
|
If you change your cgh alias to "git symbolic-ref HEAD", it'll work anywhere, not just the top level directory.
|
|
#
¿
Feb 1, 2012 01:30
|
|
|
That isn't what that's for, though, and may cause you problems later.
|
|
#
¿
Mar 3, 2012 01:14
|
|
|
You append .template or .original or somesuch to the file name and rename or copy the file during deployment.
|
|
#
¿
Apr 20, 2012 14:23
|
|
|
You can use git notes to add notes to commits. git log, git show, etc. will show them as if they were a part of the commit message.
|
|
#
¿
Apr 26, 2012 19:27
|
|
|
Bungie's contract with Activision stipulates that Activision will supply them with sufficient Perforce licenses to complete their project.
|
|
#
¿
Dec 30, 2012 10:40
|
|
|
What tools aren't respecting mailmaps?
|
|
#
¿
Oct 14, 2022 03:58
|
|
|
|
| # ¿ May 3, 2024 21:12 |
|
|
Neither CVS nor SVN required a server in the sense that there had to be a daemon listening on a port somewhere -- CVS could directly operate on a shared directory, and SVN had multiple backends including file://, [url]http://[/url] and svn+ssh://. But they did require a "server" in the sense that there was a centralized repository somewhere that did the revision control and you use a client to checkout a fragment of that to do work and all your interactions were relative to that server. Contrast that with a DVCS like git, where your local copy of the repository is a complete history of the project (ignoring things like shallow clones and git-lfs), and all your interactions are relative to your local clone. And then on top of that your local clone might have relationships to other repositories and you can use your repository to modify those other repositories.
|
|
#
¿
Oct 12, 2023 03:04
|
|