File: comment_1_bd9855cc19f0f49620258564845f1f77._comment

package info (click to toggle)
git-annex 7.20190129-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 56,292 kB
  • sloc: haskell: 59,105; sh: 1,255; makefile: 225; perl: 136; ansic: 44
file content (16 lines) | stat: -rw-r--r-- 643 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2017-05-11T17:13:35Z"
 content="""
I'm not sure that a bare repository is the best way to go about it.

One way to do it is to have a non-bare repository, which gets updated when
you push (by eg setting receive.denyNonFastforwards=false), and have that
non-bare repository be the one you push to deploy to.

While you could push first to a bare repository and have it then push on
the the non-bare repository, that seems to mostly only complicate things,
since you will need to find a way to copy the annexed file contents from
the bare to the non-bare repository.
"""]]