git

[-]

Neat compile/run cycle with git and OpenEmbedded

No matter how much careful we are when writing code, whatever changes we are making to a piece of software we must test them before production, even Donald Knuth once said: Beware of bugs in the above code; I have only proved it correct, not tried it. :).

Moreover, if the software we are working on is targeting an embedded system and needs cross-compilation and depends on other software, then testing can be more tedious: we have to prepare patches/archives and instruct the target SDK to pick our latest code, or we could code directly in the SDK working tree, but that would not be very clean. If you use git and OpenEmbedded there is a very neat way to build directly from our own working directory on the filesystem.


[-]

Branding patches with git and vim

In linux kernel development there are informal, and yet quite solid, conventions which apply when sharing patches and collaborating during the —public and undisclosed— phase of code peer-review.

As some of you may know, all the communications about kernel development happen via e-mail, and there are some tools to ease the task of preparing and sending patches; these tools allow some degree of customization, or “branding” like I am calling it in this case.

Attached images: 
ao2 X-Face

[-]

git-commit with date in the past

When setting up the git repository for VRM I wanted to preserve the project development history, but I hadn't used any real VCS tool back then, I just used to make timed backups with a scheme like this:

$ ls -1
vrm-0.1.py
vrm-0.1_237.py
vrm-0.2.py
vrm-0.3-beta-2006-03-28.py
vrm-0.3.beta-2006-05-11.py
...

[-]

ao2.it backstage: parts three and four, wiki and GIT server.

The third and fourth parts of the backstage about ao2.it are on the wiki.


[-]

git server up

in

A git server is now up at git.ao2.it.

Still not much to see there, but this is gonna change soon.