Milton Soares Filho

Tech — No comments
02
Sep 12

Finding the root device on linux

This is an example on how to find which device corresponds to your root filesystem on linux. This code was inspired by Michael Opdenacker post and related questions on StackOverflow.

#include <sys/types.h>
#include <sys/stat.h>
#include <unistd.h>
#include <assert.h>
#include <stdio.h>

int main(int argc, char *argv[])
{
    struct stat s;
    int maj, min, pmaj, pmin;
    char name[256];
    int res;

    res = stat("/", &s);
    assert(0 == res);
    maj = major(s.st_dev);
    min = minor(s.st_dev);

    FILE * f = fopen("/proc/partitions", "r");
    assert(f);

    // skip first two lines
    fscanf(f, "%*[^\n]"); fgetc(f);
    fscanf(f, "%*[^\n]"); fgetc(f);

    while (! feof(f)) {
        res = fscanf(f, " %d %d %*d %s\n", &pmaj, &pmin, name);
        assert(3 == res);
        printf("/dev/%s %d:%d%s\n", name, pmaj, pmin, (pmaj == maj && pmin == min? " *" : ""));
    }
    fclose(f);

    return 0;
}

#include <sys/types.h>

#include <sys/stat.h>

#include <unistd.h>

#include <assert.h>

#include <stdio.h>

int main(int argc, char *argv[])

{

struct stat s;

int maj, min, pmaj, pmin;

char name[256];

int res;

res = stat("/", &s);

assert(0 == res);

maj = major(s.st_dev);

min = minor(s.st_dev);

FILE * f = fopen("/proc/partitions", "r");

assert(f);

// skip first two lines

fscanf(f, "%*[^\n]"); fgetc(f);

while (! feof(f)) {

res = fscanf(f, " %d %d %*d %s\n", &pmaj, &pmin, name);

assert(3 == res);

printf("/dev/%s %d:%d%s\n", name, pmaj, pmin, (pmaj == maj && pmin == min? " *" : ""));

}

fclose(f);

return 0;

}

The output will mark the root device partition with an asterisk.

This code has the advantage of not touching all the entries at /dev as done by rdev(8) nor recursing the files under /sys/block to find the exact device, which would be a bit more complex than parsing /proc/partitions.

Tech — No comments
08
Aug 12

Quick Recipe to Enable clang_complete on Vim

It’s been a long time since my friend Thiago wisely taunted me to start using clang on vim scripts (and on everywhere else too). I finally made some time to take a look on it, mostly because of this excellent rant on the subject.

The core of the problem is that OmniCppComplete isn’t a compiler and you can’t expect something that isn’t a compiler to fully understand code. — Guy Rutenberg

So, here comes my quick recipe to get it running on vim7.3+ with python support. I assume you already have your vim setup under revision control and use pathogen to group multiple bundles (these requirements are so lame that I refuse to spend any time to justify them ).

install clang and partners

# on Ubuntu 11.10 $ sudo apt-get install clang

1
2

# on Ubuntu 11.10
$ sudo apt-get install clang

remove omnicppcomplete bundle as in this answer

$ cd ~/.vim
$ git rm --cached bundle/OmniCppComplete
$ git config -f .git/config --remove-section submodule.bundle/OmniCppComplete
$ git config -f .gitmodules --remove-section submodule.bundle/OmniCppComplete
$ git commit -a -m "remove omnicppcomplete"

$ cd ~/.vim

$ git rm --cached bundle/OmniCppComplete

$ git config -f .git/config --remove-section submodule.bundle/OmniCppComplete

$ git config -f .gitmodules --remove-section submodule.bundle/OmniCppComplete

$ git commit -a -m "remove omnicppcomplete"

create new bundle

$ git submodule add https://github.com/Rip-Rip/clang_complete.git bundle/clang_complete

1

$ git submodule add https://github.com/Rip-Rip/clang_complete.git bundle/clang_complete

fine tune clang_complete settings

# the script below is directly included by ~/.vimrc
$ cat >> ~/.vim/setup.vim
" Avoid freezing on offending code
let g:clang_user_options='|| exit 0'
let g:clang_close_preview=1
^D

# the script below is directly included by ~/.vimrc

$ cat >> ~/.vim/setup.vim

" Avoid freezing on offending code

let g:clang_user_options='|| exit 0'

let g:clang_close_preview=1

profits

$ git commit -a -m "installed clang_complete"

1

$ git commit -a -m "installed clang_complete"

Done! C/C++ code completion at the tip of your fingers.

Just as disclaimer, there are still some rough edges on the clang_complete script, e.g.

the preview window is not informative at all (better to disable with :set completeopt-=preview)
you need to manually reload source files after updating .clang_complete files (just a problem on initial setups)

However, these do not spoil the overall experience at all. The next step will be to install Ubuntu 12.04 for libclang-dev usage (much faster than using clang command).

Uncategorized — No comments
07
Aug 11

Using Textile+Trac to Manage Backlogs

After two and a half days discussing features, estimating them as a team and preparing a decent backlog, it was time to decide how to publish it. The idea of e-mailing a spreadsheet around and trying to figure out what has been modified terrrorized me. I’d like to have it an a central place where everybody could edit it and the (properly versioned) changes would be immediately available.

Whilst Google Docs could have been a nice alternative, it’d take me some time (maybe forever) to convince the managerial ranks to endorse it. Time to look for an answer closer to our company’s chest, like some internal system for managing issues related to a project, with a coupled VCS, user-based access and… Oh, wait! We already had Trac-Wiki¹ set on our project!

With an embedded VCS enabled on the wiki, the only missing feature was being capable of properly rendering backlog tables on it. The built-in wiki syntax wasn’t enough to create a functional table, however it had a WikiProcessor² extension mechanism which let me use other markups. As maintaining the backlog in pure HTML would be a pain, the alternative was to experiment a very flexible markup called Textile³.

After researching a bit of textile syntax⁴ and trying some examples, the following snippet plus a tweak at the theme style sheet rendered something near to a backlog.

{{{
#!textile
table(backlog).
|_. ID |_. Name |_. Weight |
|/2. SW01 | Feature 1 | XXX |
|\2. (acceptance criteria 1) |
|/2. SW02 | Feature 2 | XXX |
|\2. (acceptance criteria 2) |
}}}

/* CSS required */
table.backlog { border-collapse: collapse; width: 100%; }
table.backlog th {
 border: 1px solid black;
 padding: 0.5em;
 font-weight: bold;
 background-color: #ccc;
}
table.backlog td {
 border: 1px solid black;
 padding: 0.5em;
 font-size: 12px;
}

{{{

#!textile

table(backlog).

|_. ID |_. Name |_. Weight |

|/2. SW01 | Feature 1 | XXX |

|\2. (acceptance criteria 1) |

|/2. SW02 | Feature 2 | XXX |

|\2. (acceptance criteria 2) |

}}}

/* CSS required */

table.backlog { border-collapse: collapse; width: 100%; }

table.backlog th {

border: 1px solid black;

padding: 0.5em;

font-weight: bold;

background-color: #ccc;

}

table.backlog td {

border: 1px solid black;

padding: 0.5em;

font-size: 12px;

}

ID	Name	Weight
SW01	Feature 1	m
SW01	(acceptance criteria 1)
SW02	Feature 2	n
SW02	(acceptance criteria 2)

The acceptance criteria on a separate row was kind of lame, so lets try to join it with the story name.

{{{
#!textile
table(backlog).
|_. ID |_. Name |_. Weight |
| SW01 | %Feature 1% (acceptance criteria 1) | m |
| SW02 | %Feature 2% (acceptance criteria 2) | n |
}}}

/* CSS required */
table.backlog td > span:first-child { display: block; font-weight: bold; }

{{{

#!textile

table(backlog).

|_. ID |_. Name |_. Weight |

| SW01 | %Feature 1% (acceptance criteria 1) | m |

| SW02 | %Feature 2% (acceptance criteria 2) | n |

}}}

/* CSS required */

table.backlog td > span:first-child { display: block; font-weight: bold; }

ID	Name	Weight
SW01	Feature 1 (acceptance criteria 1)	m
SW02	Feature 2 (acceptance criteria 2)	n

Much better! Now, what about appending dependencies to each story? Even better, why not referencing them as links to the story itself?

{{{
#!textile
table(backlog).
|_. ID |_. Name                              |_. Weight |_. Deps |
| SW01 | %(#SW01)Feature 1% (acceptance criteria 1) | m | &nbsp; |
| SW02 | %(#SW02)Feature 2% (acceptance criteria 2) | n | &nbsp; |
| SW03 | %Feature 3% (acceptance criteria 3) | o | "SW01":#SW01  |
| SW04 | %Feature 4% (acceptance criteria 4) | p        | &nbsp; |
| SW05 | %Feature 5% (acceptance criteria 5) | q        | "SW01":#SW01, "SW02":#SW02 |
| SW06 | %Feature 6% (acceptance criteria 6) | r        | &nbsp; |
}}}

{{{

#!textile

table(backlog).

| SW01 | %(#SW01)Feature 1% (acceptance criteria 1) | m |   |

| SW02 | %(#SW02)Feature 2% (acceptance criteria 2) | n |   |

| SW03 | %Feature 3% (acceptance criteria 3) | o | "SW01":#SW01 |

| SW04 | %Feature 4% (acceptance criteria 4) | p |   |

| SW05 | %Feature 5% (acceptance criteria 5) | q | "SW01":#SW01, "SW02":#SW02 |

| SW06 | %Feature 6% (acceptance criteria 6) | r |   |

}}}

ID	Name	Weight	Deps
SW01	Feature 1 (acceptance criteria 1)	m
SW02	Feature 2 (acceptance criteria 2)	n
SW03	Feature 3 (acceptance criteria 3)	o	SW01
SW04	Feature 4 (acceptance criteria 4)	p
SW05	Feature 5 (acceptance criteria 5)	q	SW01, SW02
SW06	Feature 6 (acceptance criteria 6)	r

The   hack, used to prevent column spanning, may not be required in Trac as it is in my wordpress processor.

To finish a fancy and useful backlog we can add two classes to visualize the separation of stories per sprint. Those without a background color are still in the project’s pipeline.

{{{
#!textile
table(backlog).
        |_. ID |_. Name                              |_. Weight |_. Deps |
(odd).  | SW01 | %(#SW01)Feature 1% (acceptance criteria 1) | m | &nbsp; |
(odd).  | SW02 | %(#SW02)Feature 2% (acceptance criteria 2) | n | &nbsp; |
(even). | SW03 | %Feature 3% (acceptance criteria 3) | o | "SW01":#SW01  |
(even). | SW04 | %Feature 4% (acceptance criteria 4) | p | &nbsp; |
(odd).  | SW05 | %Feature 5% (acceptance criteria 5) | q | "SW01":#SW01, "SW02":#SW02 |
| SW06 | %Feature 6% (acceptance criteria 6) | r        | &nbsp; |
}}}

/* CSS required */
table.backlog tr.odd { background-color: #ddd }
table.backlog tr.even { background-color: #ffa }

{{{

#!textile

table(backlog).

(odd). | SW01 | %(#SW01)Feature 1% (acceptance criteria 1) | m |   |

(odd). | SW02 | %(#SW02)Feature 2% (acceptance criteria 2) | n |   |

(even). | SW04 | %Feature 4% (acceptance criteria 4) | p |   |

(odd). | SW05 | %Feature 5% (acceptance criteria 5) | q | "SW01":#SW01, "SW02":#SW02 |

| SW06 | %Feature 6% (acceptance criteria 6) | r |   |

}}}

/* CSS required */

table.backlog tr.odd { background-color: #ddd }

table.backlog tr.even { background-color: #ffa }

ID	Name	Weight	Deps
SW01	Feature 1 (acceptance criteria 1)	m
SW02	Feature 2 (acceptance criteria 2)	n
SW03	Feature 3 (acceptance criteria 3)	o	SW01
SW04	Feature 4 (acceptance criteria 4)	p
SW05	Feature 5 (acceptance criteria 5)	q	SW01, SW02
SW06	Feature 6 (acceptance criteria 6)	r

With this template and relatively simple syntax, it seems easier to create, delete and move stories around. Modifications can be figured out at Trac’s page history and things get associated by the hyperlinks. Good bye, nasty spreadsheets!

Other advantage is that if you don’t use Trac for your projects, the only thing you need is a textile processor to get it done. You may auto-generate it from build-scripts, use another bug-tracker or integrate into WordPress (as I did it here).

A downside in this alternative is the need to specify custom CSS rules outside of textile content. I had to hack it into WordPress current theme’s style sheet and into Trac’s too. Look at the complete excerpt below.

table.backlog { border-collapse: collapse; width: 100%; }
table.backlog th {
 border: 1px solid black;
 padding: 0.5em;
 font-weight: bold;
 background-color: #ccc;
}
table.backlog td {
 border: 1px solid black;
 padding: 0.5em;
 font-size: 12px;
}
table.backlog td > span:first-child { display: block; font-weight: bold; }
table.backlog tr.odd { background-color: #ddd }
table.backlog tr.even { background-color: #ffa }

table.backlog { border-collapse: collapse; width: 100%; }

table.backlog th {

border: 1px solid black;

padding: 0.5em;

font-weight: bold;

background-color: #ccc;

}

table.backlog td {

border: 1px solid black;

padding: 0.5em;

font-size: 12px;

}

table.backlog td > span:first-child { display: block; font-weight: bold; }

table.backlog tr.odd { background-color: #ddd }

table.backlog tr.even { background-color: #ffa }

References

¹ Trac Wiki webpage

² Wiki Processors

³ Textile homepage

⁴ Hobix Textile Reference

UPDATE: better colors and avoid selecting spans after the first one.

Uncategorized — 2 comments
25
Feb 11

Classificados Tocantins

Eu e minha esposa estamos nos preparando para migrar de Manaus, portanto resolvemos nos desfazer de alguns bens que nÃ£o iremos levar.

SÃ£o todos itens adquiridos desde 2007, com estado de conservaÃ§Ã£o razoÃ¡vel. Estamos colocando as fotos aos poucos pra agilizar, mas quem quiser dar uma olhada, por favor, entre em contato (pode ser pelos comentÃ¡rios aqui no blog mesmo ou pelo meu celular, caso me conheÃ§a).

Detalhe: os itens mais essenciais, como geladeira e fogÃ£o, sÃ³ poderemos entregar a partir do dia 12/03/11, que Ã© quando devemos fazer a mudanÃ§a para o novo “lar de transiÃ§Ã£o“.

Cozinha

~~FogÃ£o Mueller 4 bocas~~	150.00
MÃ¡quina lava-roupas Electrolux 8kg	550.00
Liquidificador Mondial Ultramix 3 com coador	45.00
Geladeira Electrolux Frost Free DF37	900.00
Rack Fruteira Cozinha	110.00
~~Bebedouro Refrigerador Mallory~~	180.00
~~Micro-ondas Electrolux~~	150.00
ArmÃ¡rio AlumÃnio Colormaq Cozinha 3 portas	320.00
~~Grill George Foremann mÃ©dio com estufa para pÃ£o~~	100.00

Sala

~~Rack grande~~	290.00
Rack pequeno	90.00
~~SofÃ¡ Branco 3 lugares~~	400.00
~~Mesa com banquetas~~	150.00
~~Mesa retangular dobrÃ¡vel~~	110.00
Mesa p/ computador	50.00
~~TV Sony LCD Bravia 32pol~~	850.00
TV Philips tubo 21pol	150.00
CÃ¢mera Digital Kodac 4MegaPixel C433 + 512MB	150.00
DVD player philips DVP320	70.00
Caixa Som + Subwoofer 2.1 Clone com entrada celular	180.00
~~Ventilador Seville Classic torre giratÃ³ria~~	165.00
Bicicleta Caloi 18 marchas T-Type com acessÃ³rios	700.00

Quarto

~~Ar condicionado Consul 7500~~	300.00
~~Ar condicionado Eletrolux 7500 c/ controle~~	420.00
~~Ferro Walita~~	40.00
TÃ¡bua de Passar	40.00
Maca para estÃ©tica branca	300.00
~~Vitrine vidro 6 mÃ³dulos~~	250.00
Cabideiro/Arara	120.00
~~Sapateira 2 portas 4 estantes~~	120.00
ColchÃ£o Solteiro Probel 12cm	50.00
Apoio TriÃ¢ngulo	60.00

Tech / Uncategorized — 2 comments
20
Jan 11

Hiding that horrible tabline in Vim

Long time no post in here, sorry.

Since I’ve had the chance to review Kim Schulz’s Hacking Vim 7.2 ebook¹ and a friend of mine started using vim as his main development tool, digging into Vim’s configurations and flavours has become somewhat even more pleasant.

In an attempt to improve my performance when editing various files, I’m trying to use tabpages instead of only several windows. It’s been working as some kind of context stack for me, as there can be one tabpage (probably with fewer windows) for modifying files from a project and another tabpage for a different but related one (or a non-related task in the same project). Plus, using more tabpages and less windows can save precious screen space.

But what to do about that odious tabline which, besides hurting my sense of aesthetics, eats a whole line of the screen? Thankfully to the Vim’s extremely flexible nature, it didn’t take long to find an answer. It came in form of disabling the tabline entirely and putting its only usable information into the statusline. Used a bit of scripting to overcome the only corner case I could think of and took the chance to try my rusty skills on python + vim bindings. Pretty much everything someone will need to put both domains together is in this little example (besides the vim module complete API, easily accessible by issuing :h python).

function! MyTabMarker(disable)
python << EOF
import vim
def tabpagecount():
        return int(vim.eval("tabpagenr('$')"))
def tabpage():
        return int(vim.eval("tabpagenr()"))
def tabmark():
        disable = int(vim.eval("a:disable"))
        if tabpagecount() > 1 and not disable:
                return "\"[tab %d/%d] \"" % (tabpage(), tabpagecount())
        return "\"\""
vim.command("return " + tabmark())
EOF
endfunction

set laststatus=2
set showtabline=0
set statusline=#%02n\ %{MyTabMarker(0)}%f\ %m%r%y%=\(%bd,%Bh)\ %c,%l/%L\ %P

function! MyTabMarker(disable)

python << EOF

import vim

def tabpagecount():

return int(vim.eval("tabpagenr('$')"))

def tabpage():

return int(vim.eval("tabpagenr()"))

def tabmark():

disable = int(vim.eval("a:disable"))

if tabpagecount() > 1 and not disable:

return "\"[tab %d/%d] \"" % (tabpage(), tabpagecount())

return "\"\""

vim.command("return " + tabmark())

EOF

endfunction

set laststatus=2

set showtabline=0

set statusline=#%02n\ %{MyTabMarker(0)}%f\ %m%r%y%=\(%bd,%Bh)\ %c,%l/%L\ %P

There you see how to pass arguments into python methods and how to feed values back from it to the vim environment. Eventually I’ll publish my entire .vimrc with comments so everyone can rant about how theirs way is better

[1] as I’ve lost my notebook due to a robbery at the technical assistance, my review annotations were lost too. I’ll need to re-review the book to get something published about it then.

Planet INdT / Tech — 6 comments
28
May 10

gource: OpenGL-based 3D visualisation tool for source control repositories

Too much fun the tool I’ve came to know through my friend Adenilson’s blog. In a glance one can explore effort put into a project in a way much better than any other command-line or graphical application known.

The only boring thing is to use it in my machine, a hp pavilion dv4-2167sb, which, AFAIK, still lacks a good graphical acceleration support.

I’ve made a very basic debian package (using checkinstall) for people too lazy to compile/install by themselves.

Enjoy it and have fun!

Uncategorized — 5 comments
21
Mar 10

Vendo Minha Moto

Sorry, available only in pt_BR.

Num esforÃ§o de desapego, decidi passar pra frente minha fiel companheira… de estrada. Ã� isso, pra quem se acostumou a me ver junto da minha mÃ¡quina atravessando o Brasil e registrando no site do RockPesado, saiba que nÃ£o faÃ§o isso por desgosto, mas simplesmente por adequaÃ§Ã£o, jÃ¡ que nÃ£o pretendo trazÃª-la novamente para Manaus-AM para negar-lhe os prazeres que uma moto estradeira merece (asfalto bom, vÃ¡rias opÃ§Ãµes de destino, peÃ§as a pronta entrega, enfim, tudo que alguÃ©m morando no Sul ou Sudeste tem de sobra).

Minha moto Ã© uma Honda Shadow e foi apelidada de UÃ¡kti, em homenagem a lenda do belo e encantador Ãndio que, apÃ³s ressucitar de uma morte com vÃ¡rias flechadas, emitia um som de flauta quando o vento transpassava seu corpo, atraindo ainda mais as mulheres das tribos e provocando mais inveja dos homens. Abaixo uma breve ficha tÃ©cnica:


Marca: Honda Shadow VT600C
Ano: 2002
Cor: cinza
Quilometragem: 63.000 km
Ã�ltimas trocas:
  - Corrente, coroa e pinhÃ£o (CoCoPi): 55.000 km
  - Pneu traseiro: ~55.000 km
  - Pneu dianteiro: ~57.000 km
  - Filtro de ar: ~60.000 km

Como toda moto custom que se preze, traz vÃ¡rios acessÃ³rios estendendo suas configuraÃ§Ãµes originais.

Sissy-bar com bagageiro
Banco remodelado (feito pelo lendÃ¡rio Peninha, artesÃ£o de estofamentos de Curitiba-PR)
Comando avanÃ§ado
Protetor de cÃ¡rter (peito de aÃ§o)
Protetor do reservatÃ³rio de Ã¡gua (ponto fraco das Shadow)
Mata-cachorro
FarÃ³is de milha com lanterna
Alforges laterais (surrados, mas ainda bem usÃ¡veis)
e mais alguns detalhes mais estÃ©ticos que funcionais (saia reduzida na placa traseira, tampÃ£o cromado do retificador, suporte extra na grade da refrigeraÃ§Ã£o, etc)

E tem mais, quem ligar agora leva tambÃ©m um conjunto de cÃ¢meras (dianteira e traseira) dos pneus de brinde! Totalmente grÃ¡tis! – momento polishop

Pra quem estiver interessado, ela se encontra em Curitiba na casa do meu pai. Pra apreciaÃ§Ã£o, mande-me um e-mail que arranjo a visita.

Essa moto Ã© guerreira, jÃ¡ me levou em seguranÃ§a por todo o litoral do Brasil e do Uruguai, sobreviveu a hostilidade da polÃcia Argentina e cortou tranquilamente todo o Centro-Oeste brasileiro, inclusive passando pela capital federal. Portanto nÃ£o estranhe se ela reclamar quando tirÃ¡-la de casa pra andar menos de 200km!

Misc — 1 comment
08
Oct 09

Sale

Sorry, this entry is only available in PortuguÃªs Brasil.

Planet INdT — 1 comment
17
Jun 09

Qt/openBossa Challenge

Nice opportunity to win a Nokia N810 tablet at the FISL. (Free translation from pt_BR)

Do you have a good idea? Do you know the Qt library? Would you like to be awarded for that?
The INdT (Nokia Technology Institute), nowadays one of the main development excellence centers in Brazil, promotes the first Qt/openBossa challenge.
We look for developers capable of putting your ideas into practice and build Qt applications designed to Nokia’s mobile devices. Participants will create innovations which will be evaluated and awarded during the 10th International Free Software Forum (FISL).

More at http://openbossa.org/fisl/index.html.

Planet INdT — 1 comment
14
Jun 09

Qt Codestyle Automatic Check

Code style carries many benefits, such as improved maintainability and support for a rich Coding Standard. However it’s not safe to rely on developers to always comply to style rules along the source code, that’s why automatic code style verification should be an initial concern for professional-level works.

For the sake of coding-style-importance-aware people, there are many great projects such as GNU indent, pep8 and astyle that perform all the work for you, whose only need the appropriate setup flags.

For Qt projects, astyle is the recommended tool. But there are a few drawbacks on using it.

it’s too intrusive. astyle performs code modification in-line, disturbing the repository sources instead of serving as a verification tool only
weak didactic factor. Unlike pep8 script, which tells the developer exactly what the problem is and contributes to avoid it at the future (as a lesson learned effect)
it’s output can not be easily integrated with another tools

I’ve created a shell script in order to overcome some of the previous issues. It’s available here. Some relevant features.

quickfix-style list output
QTest style output at the end
Ignore moc created files
All suggested modifications can be applied as one patch, directly available to the user
Can be run inside a testsuite (make test) or as a standalone program

TODO

try to extend astyle classes
allow alternative code styles
better source selection schema (integrated with qmake, maybe?)
fix-up improper indentation on some important macros (foreach, .e.g.)
test and make it work on MacOS

Milton Soares FilhoRandom rants and SW developers’ stuff

Finding the root device on linux

Quick Recipe to Enable clang_complete on Vim

Using Textile+Trac to Manage Backlogs

References

Classificados Tocantins

Cozinha

Sala

Quarto

Hiding that horrible tabline in Vim

gource: OpenGL-based 3D visualisation tool for source control repositories

Vendo Minha Moto

Sale

Qt/openBossa Challenge

Qt Codestyle Automatic Check

Language | Idioma

Tags

Blogroll

Meta

Milton Soares FilhoRandom rants and SW developers’ stuff

References

Cozinha

Sala

Quarto

Find Myself

Language | Idioma

Tags

Blogroll

Meta