Commit | Line | Data |
a326c00a |
1 | =head1 NAME |
2 | |
3 | Gitalist::Faq - Frequently asked questions about Gitalist |
4 | |
5 | =head1 QUESTIONS |
6 | |
7 | =head2 Is there a Gitalist demo site anywhere |
8 | |
9 | See L<http://goatse.co.uk/~bobtfish/Gitalist/script/gitalist.fcgi/> |
10 | |
11 | =head2 Is there anything that explains what the color bars under the SHA-1 hashes mean? |
12 | |
13 | They don't mean anything as such, they're just first 6 chars of the |
14 | SHA-1 as a hex colour e.g the commit |
15 | C<< f85cb28d32054b92e2a7094a83ebe528485dbf36 >> becomes C<< #f85cb2 >> |
16 | hence that pink colour you see. It was an idea borrowed from Chroma-Hash |
17 | (L<http://mattt.github.com/Chroma-Hash/>). |
18 | Also at the top right hand corner of pages is the first 36 chars of |
19 | the SHA-1 of the current commit where the color underneath each 6 char |
20 | chunk is the corresponding hex colour. I've found the colours to be a |
21 | handy visual cue when dealing with SHA-1s. |
22 | |
23 | =cut |
24 | |
25 | =head1 SEE ALSO |
26 | |
27 | L<Gitalist> |
28 | |
29 | =head1 AUTHORS |
30 | |
31 | See L<Gitalist> for authors. |
32 | |
33 | =head1 LICENSE |
34 | |
35 | See L<Gitalist> for the license. |
36 | |
37 | =cut |
38 | |