comment and improve docs
This commit is contained in:
parent
43271632af
commit
cf85d54a2f
2 changed files with 13 additions and 0 deletions
|
@ -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.
|
||||
"""]]
|
|
@ -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
|
||||
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:
|
||||
|
||||
* Make some changes to files in the repository, using `git-annex`,
|
||||
|
|
Loading…
Reference in a new issue