On Thu, Nov 14, 2019 at 04:55:37PM +0100, Machiel Kolstein wrote: [...] >> Actually I have no idea how so solve this (I do not use Github) but [2] >> appears to explain all that stuff and provide a solution. [...]
> But, do I understand correctly that "Git" is not equivalent to > "GitHub"? I.e., one can use Git without using "Github"? That is correct: Git is a piece of free software software which implements a particular version control system (VCS) while Github is a proprietary hosting solution offering — among other things — certain approach to making contributions to other people's work and manage such contributions. To understand the distinction, you should first grasp the idea is that any repository operated by Git is completely self-contained and free-standing: it is a set of files kept in a designated directory on a computer's file system, and it requires nothing but the installed Git software to be operated on. While Git's core is agnostic to the way you may introduce changes to a repository, it's certainly convenient to have ways to communicate work between different Git repositories; most of the time these are (almost) "mirrors" of the same repository, but this is not a requirement, and in advanced workflows exchange of work between unrelated repositories is sometimes used. Git supports several "transports" to make Git processes managing different repositories communicate with each other. A special protocol implemented via HTTP[S] requests is one of them; two instances of Git are also able to talk to each other via SSH. This feature makes it possible to run "low-tech" "remote hosting" of Git repositories: basically all you need to do that is a box running a Unix-like operating system with the SSH server and Git installed there; making Git available via HTTP[S] in such a setup is a bit more complicated but certainly doable. Still, there exist "turn-key" remote hosting solutions which usually combine actual hosting of Git repositories — accessible by Git you run on your computer, — and a rich web interface for both repository management and a way to facilitate collaboration on the content hosted in those repositories. Github is arguably the largest proprietary Git hosting solution, but other big players do exist (Bitbucket and GitLab to name a few), and more simple solutions do exist as well — including those you can deploy privately on your own premises. To recap, Github is certainly not needed to work with Git (and the two top projects using Git — the Linux kernel and Git itself — do not use Github for their workflow and hosting, though they keep readonly mirrors there). -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/20191114162406.jpxy4ls7zzwzmd4w%40carbon.
