Because for technical and legal reason the usage of a central repository is for some projects not possible, I would like to set up the versioning with Git in a peer to peer fashion without a catalyzing server. How could this be done?
Asked
Active
Viewed 4,805 times
3 Answers
3
This would mean sending patches, through for instance email.
See "Git Tip of the Week: Patches by Email"
One way of getting changes is by providing a patch, or a set of changes which can be applied to a remote repository at the other end.
Git started life as a distributed version control system for the Linux project, which actively uses mail lists both as a discussion mechanism and also as a distribution mechanism for patches (changes) for an existing codebase. (New features are just a special case of patching nothing to add the new code.)
Another option is to email a git bundle, which can be incremental.
It is one file, and you can fetch from it.
It is different from a patch.
3
git daemon might be what you are looking for.
Beware that this mechanism exposes your project to the network as it does not have authentication mechanism.
nshimiye
- 144
- 1
- 4
2
When Git used in pure DVCS-mode, it's the same (technically) thing, as using in pseudo CVCS-mode
- Each side have any possible publishing method, which it can provide (ssh://, git://, http://) in order to be reachable from remote
git cloneand|orgit remote addestablish relations between nodes (1:many)git pull|git pushwill transfer changesets between nodes
Lazy Badger
- 91,325
- 7
- 76
- 105
-
what publishing method do you think makes most sense for a number of laptops over WLAN? – Raffael Jun 30 '14 at 05:45
-
@Raffael - *any implementable* (ssh is hard in Windows, http require http-server) – Lazy Badger Jun 30 '14 at 06:21