3 Just in case somebody finds this blog, here is a challenge. Inspired by my
4 own little hack (this blog), I announce the "Using Git For What It Is Not
7 And it is especially cool, since the acronym sounds cool! You might miss
8 this fact if you do no know that I pronounce the "F" like an "A" so that
11 This will be a running contest; whenever I have 10 valid applications, I
12 will announce a winner on the Git mailing list.
14 So, what accounts for a valid application?
17 <li> You must use a Git program (the term is used loosely here, GitWeb is
18 considered a Git program, for example).
19 <li> The program must be intended for something completely different than
20 what you are using it for. E.g. GitWeb -- which was intended to let
21 you browse through the history using your web browser -- is used
22 to serve a blog to the wide world.
23 <li> You must be able to prove that you actually used the Git program to
24 the purpose you claim, preferably in a live demonstration like this
26 <li> Nobody and nothing must be harmed in the process (except your
27 laughing muscle, that's okay).
30 So, how does such an abuse look like?
33 <li> ... like this blog.
34 <li> Managing your mail (in maildir format) in a Git repository.
35 <li> Finding duplicate files by
39 $ git ls-files --stage | sort -k2 | uniq -d -s7 -w40
41 <li> Abusing the Git alias mechanism to call scripts defined directly in
45 I am really looking forward to all of your submissions... *chuckles*