That's my way to see how RavenDB is working. Whenever you commit something to the repository, I inspect the changes and try to understand them. This way I can see if it might break my code, and I think I learn something too. Additionally I may see an error on occasion as the one above, and a direct comment on GitHub seemed to be the most appropriate way for reporting.
The only thing I still need is pull requests on existing issues, then there is nothing that stops me to do the next larger project we tackle with the aid of a private repository in github :)
I like to use Codebase HQ for private team based projects -
http://www.codebasehq.com/ - lots of nice features although, I have not seen specific line notes like you are showing here.
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Horizontal Rules
Three or more dashes or asterisks:
---
* * *
- - - -
Manual Line Breaks
End a line with two or more spaces:
Roses are red,
Violets are blue.
Fenced Code Blocks
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Header IDs
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Tables
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |Yellow
Definition Lists
Term 1
: Definition 1
Term 2
: Definition 2
Footnotes
Body text with a footnote [^1]
[^1]: Footnote text here
Abbreviations
MDD <- will have title
*[MDD]: MarkdownDeep
FUTURE POSTS
Partial writes, IO_Uring and safety - about one day from now
Configuration values & Escape hatches - 5 days from now
What happens when a sparse file allocation fails? - 7 days from now
NTFS has an emergency stash of disk space - 9 days from now
Challenge: Giving file system developer ulcer - 12 days from now
And 4 more posts are pending...
There are posts all the way to Feb 17, 2025
RECENT SERIES
Challenge
(77): 20 Jan 2025 - What does this code do?
Answer
(13): 22 Jan 2025 - What does this code do?
Comments
That's my way to see how RavenDB is working. Whenever you commit something to the repository, I inspect the changes and try to understand them. This way I can see if it might break my code, and I think I learn something too. Additionally I may see an error on occasion as the one above, and a direct comment on GitHub seemed to be the most appropriate way for reporting.
shouldn't the 't' be a 'w'
;)
The only thing I still need is pull requests on existing issues, then there is nothing that stops me to do the next larger project we tackle with the aid of a private repository in github :)
I like to use Codebase HQ for private team based projects - http://www.codebasehq.com/ - lots of nice features although, I have not seen specific line notes like you are showing here.
Never had a chance to use this, but i keep it bookmarked just in case. http://code.google.com/p/rietveld/
Comment preview