fix #19

[maboiteaspam]

Restore original Markdown formatting.

[maboiteaspam]

I m not really sure if i should go further in the release process ? And in that eventuality, how to proceed.

Anyway, they look really cool now

• [23efb05cc3] - doc: document fs.watchFile behaviour on ENOENT (Brendan Ashworth) #2093
• [1afc0c9e86] - fs: fix error on bad listener type (Brendan Ashworth) #2093

Too bad I dropped that error into the source.

[rvagg]

lgtm, just stop short of bumping version and publishing, I'll hang on to that responsibility for now

[maboiteaspam]

sure.

I m buggy about the last comment made by some guys on iojs project, about the missing commits.

Should i just checkout io project and run the command then check the commits listed to figure out ?

[rvagg]

Yeah, missing commits, ignore that for now, it's not relevant for this but it is an interesting problem that I'd love to find a solution to.

Basically if you have multiple branches and tag on them, like this:

branch1 ----- a ----- c -------------------------

branch2 --- b ------------- d -------------------

and you want to do a changelog-maker on branch1 from tag c to the current HEAD you will only get commits from the time of tag d onwards even though it's on a completely different branch. This is because we just look at the list of tags, regardless of which branch they are on and use the time of the latest tag as our starting point.

It's solvable now by using changelog-maker --start-ref=c, but as we do more multi-branch releases in io.js this is increasingly becoming a problem.

So we need a way to list tags on the current branch only, ignoring other branches.

[maboiteaspam]

OK, thanks a lot for explanations ! I ll try to figure out about it.

[rvagg]

happy for you to merge this btw then I can cut a new relesae