mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment and improve docs

Browse source
This commit is contained in:
Joey Hess 2023-04-19 12:20:26 -04:00
parent 43271632af
commit cf85d54a2f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/git-annex-sync/comment_7_8f9a5457020bed293e9a93ccc9461a65._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="joey"
subject="""Re: Sync to remote master?"""
date="2023-04-19T16:17:11Z"
content="""
The push to remote master will typically fail in a non-bare repository
(it is possible to configure one to allow it). The push to synced/master
will then succeed. Then when sync is later run in that repository, it will
merge synced/master into master.
"""]]

3
doc/sync.mdwn
View file

@ -29,6 +29,9 @@ to every other repository; as long as the graph of repositories is
connected, and `git annex sync` is run from time to time on each, a given connected, and `git annex sync` is run from time to time on each, a given
change, made anywhere, will eventually reach every other repository. change, made anywhere, will eventually reach every other repository.
(`git-annex sync` will also attempt to push the master branch to remotes,
which does work for bare repositories.)
The workflow for using `git annex sync` is simple: The workflow for using `git annex sync` is simple:
* Make some changes to files in the repository, using `git-annex`, * Make some changes to files in the repository, using `git-annex`,