+972 52-548-6969
Originally posted at 1/17/2011
Occasionally I get asked what code review tools I use.
The truth is, I tend to use TortoiseGit’s Log Viewer and just read the history, but I am not leaning toward this baby:
This is really nice!
Markdown turns plain text formatting into fancy HTML formatting.
*italic* **bold**
_italic_ __bold__
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Three or more dashes or asterisks:
---
* * *
- - - -
End a line with two or more spaces:
Roses are red,
Violets are blue.
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowTerm 1
: Definition 1
Term 2
: Definition 2Body text with a footnote [^1]
[^1]: Footnote text here
MDD <- will have title
*[MDD]: MarkdownDeep
And 2 more posts are pending...
There are posts all the way to Jul 04, 2017
| Main feed |
|
| Comments feed | |
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