Yeah dog pretty much everything on the github website is an interface to display info held in the .git folder of the website.
Thats how theres github, gitlab, gitea, gitlab, forgejo, etc etc. There are even applications you can download to visualize info in git that run on your local machine, and only see youe local filesystem.
Maybe what I misunderstood is where git ends and github starts. I know there are other hosting platforms, and I’ve used a lot of git visualizers. But what I’ve never tried to do is use git with multiple developers without connecting to some 3rd party server. Is there some peer to peer functionality built into git or did I totally misunderstand your original comment? Or are you literally sharing the git folder via network file system, thumb drive, etc?
Git doesn’t have a concept of a preferred repository; your local copy is exactly as valid to git as a git server hosted on github.
The originally intended workflow as I understand it involved generating patches which would be shared via a mailing list.
In practice there will generally be a repository that’s considered “canonical” for a project, whether that’s the one on the computer of the lead maintainer or some hosted solution.
Yeah dog pretty much everything on the github website is an interface to display info held in the .git folder of the website.
Thats how theres github, gitlab, gitea, gitlab, forgejo, etc etc. There are even applications you can download to visualize info in git that run on your local machine, and only see youe local filesystem.
Maybe what I misunderstood is where git ends and github starts. I know there are other hosting platforms, and I’ve used a lot of git visualizers. But what I’ve never tried to do is use git with multiple developers without connecting to some 3rd party server. Is there some peer to peer functionality built into git or did I totally misunderstand your original comment? Or are you literally sharing the git folder via network file system, thumb drive, etc?
Yes the original use case is sending patches back and forth on the Linux kernel mailing list
Git doesn’t have a concept of a preferred repository; your local copy is exactly as valid to git as a git server hosted on github.
The originally intended workflow as I understand it involved generating patches which would be shared via a mailing list.
In practice there will generally be a repository that’s considered “canonical” for a project, whether that’s the one on the computer of the lead maintainer or some hosted solution.
A basic git server is essentially just a repository owned by a restricted user with SSH access granted to maintainers.. This can allow users to push and pull from a centralised or semi-centralised repository in much the same way as GitHub.