File: gitify.chk

package info (click to toggle)
reposurgeon 4.38-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 23,500 kB
  • sloc: sh: 4,832; makefile: 514; python: 485; lisp: 115; awk: 91; ruby: 19
file content (110 lines) | stat: -rw-r--r-- 1,924 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
#reposurgeon sourcetype svn
blob
mark :1
data 210
# A simulation of Subversion default ignores, generated by reposurgeon.
*.o
*.lo
*.la
*.al
*.libs
*.so
*.so.[0-9]*
*.a
*.pyc
*.pyo
*.rej
*~
*.#*
.*.swp
.DS_store
# Simulated Subversion default ignores end here

blob
mark :2
data 13
Lorem ipsum.

commit refs/heads/master
#legacy-id 2
mark :3
committer esr <esr> 1513334797 +0000
data 116
This is a boringly typical example of a run-on content which should
*not* be broken after the first line by gitify.
M 100644 :1 .gitignore
M 100644 :2 READ.ME

blob
mark :4
data 29
Lorem ipsum.
dolor sit amet.

commit refs/heads/master
#legacy-id 3
mark :5
committer esr <esr> 1513334948 +0000
data 131
This is a Subversion comment that *should* be broken after the first line.

It ends with a period, which is one of gitify's clues.
from :3
M 100644 :4 READ.ME

blob
mark :6
data 58
Lorem ipsum.
dolor sit amet,
consectetur adipiscing elit,

commit refs/heads/master
#legacy-id 4
mark :7
committer esr <esr> 1513335053 +0000
data 58
Check that gitify doesn't futz with single-line comments.
from :5
M 100644 :6 READ.ME

blob
mark :8
data 126
Lorem ipsum.
dolor sit amet,
consectetur adipiscing elit,
sed do eiusmod tempor incididunt ut labore et dolore magna alicqua.

commit refs/heads/master
#legacy-id 5
mark :9
committer esr <esr> 1513335237 +0000
data 106
Verify that we also break run-on comments on a comma,

which is considered a line-ender for this purpose.
from :7
M 100644 :8 READ.ME

blob
mark :10
data 151
Lorem ipsum.
dolor sit amet,
consectetur adipiscing elit,
sed do eiusmod tempor incididunt ut labore et dolore magna alicqua.
Ut enem ad minim veniam,

commit refs/heads/master
#legacy-id 6
mark :11
committer esr <esr> 1513335349 +0000
data 136
Check that we do not mess with a comment that already has a separator line.

Even if it had a period which would normally trigger that.
from :9
M 100644 :10 READ.ME

done