* Advent of Code repo

I decided the structure will be as follow:
.
├── year
│  ├── a
│  │  ├── a.py
│  │  └── input.txt
│  ├── b
│  │  ├── b.py
│  │  ├── input.txt
│  ├── c
│  │  ├── c.py
│  │  └── input.txt
│  ├── d
│  ├── e
│  └── ownerproof_token
├── year+1
│  ├── a
│  │  ├── 1.py
│  │  ├── 2.py
│  │  ├── input.txt
│  │  ├── refinement.org
│  ├── b
│  │  ├── 1.py
│  │  ├── 2.py
│  │  └── input.txt
│  └── c
├── year+n
│  ├── a
│  │  ├── a.erl
│  │  ├── input.txt
│  │  └── text.org
│  └── ownerproof_token
└── README.org

The days are mapped onto alphabetic letters.
day 1 -> a, day 2 -> b, ...
Rationale:
- The letters are easier to reach than digits (close to homerow for a good amount of them)
- have a smaller length (so faster to type),
- you can't get it wrong as opposed to numbers (3 or 03 to get a correct sorting in ls, and github, and ... at the same time ?)
- It makes you remember better the alphabetical order, which might be useful

When you solve the day in one file, this file should be named <letter>.<ext>
When you separate part 1 and part 2 to solve it, it should be named 1.<ext> and 2.<ext>


* DVCS Scenario

Hi everyone, i wanted to try advent of code, and i was wondering if doing it this way would be possible 

1. First commit on master branch (add README, gitignore, ...)
2. create dir for year and day1, and add input.txt
3. commit on master
4. create a branch for <your_lang>
5. write your solution, and commit in the branch.
6. Back into master, the solution file shouldn't be visible anymore
7. If we create a branch for another language, we can solve it in the same way, and not see it when back on master
8. If we create day2 dir in master, and add input.txt, then go into a language branch, we should be able to see day2/input.txt, even if the input.txt has been added after the creation of the <lang branch>. This should preferably be possible without merging master into the <lang> branch.

** git

I forgot to copy-paste conversation, but basically it was along the lines of:
You have to rebase, merge, or something else (probably equivalent to cherry-picking)

** hg

<Zash> tamwile`, no, files added on one branch don't show up on other branches
       without a merge.  [14:42]
<Zash> unless they were added before the branch point

** darcs

Is this sort of setup would be possible with darcs ?  [16:31]

Correct english:
Would this sort of setup be possible with darcs ?

<gpiero> tamwile`: darcs does not support in-directory branches  [19:18]
<gpiero> I think Ben had some plans for implementing them, but don't know the
         status at the moment
<gpiero> when someone talks about darcs' branches, they probably mean separate
         repos that share a common context  [19:19]
<gpiero> in this sense, all darcs repos are branches of a single repo
         representing the empty context
<gpiero> back to your example, creating day2 in master has no effect in
         branches, being them separate repos  [19:21]
<gpiero> you have to pull/push patches between them (so called 'master' and
         'branches') in order to let 'branches' know about changes in
         'master', and the other way around


** pijul