Tarin Gamberini

A software engineer and a passionate java programmer

The Best of Git working with Subversion

Usually to interact between a remote Subversion repository and a local Git repository you have to be on the local master branch and run:

  • git svn dcommit instead of git push
  • git svn rebase instead of git pull --rebase

There is no equivalent to git pull because Subversion and Git handle merges differently, so to prevent Subversion committers saw merge commits a rebase is mandatory.

You can get the best of Git working with Subversion interacting between the Git local repository and the local working directory.

So you can:

  • preparing to commit only the part of a file you want, by using git add --patch
  • rewriting commit history, by using git rebase --interactive and the various pick, reword, edit, squash, fixup
  • extremely quickly create new branches
  • including in the current branch a single commit made on another branch, by using git cherry-pick
  • using git bisect to find which commit caused a particular bug
  • temporarily parking last changes to face an emergency, by using git stash save my_current_issue

and do all the other stuff you can do locally that make you love Git.

I want to stress about using local branches to your benefit only and not to collaborate with other committers. This means you have to merge locally your branches into master before interacting with remote subversion repository. In this way no one could see your merge commits.

Committee about the Italy's guidelines for the CAD's Art 68

Italian government on December 2012 changed the art. 68 of the eGovernment Code (Codice dell'Amministrazione Digitale (in Italian)) (CAD) indicating to public administrations (PA) the obligation to prefer Free Software assessing software acquisition.

The novelty aspect of the new art.68 (it) lies in comma 1-ter where is stated that “proprietary software acquisition with user license” (“l'acquisizione di programmi informatici di tipo proprietario mediante ricorso a licenza d'uso”) is permitted only if

it is motivationally impossible to get existing solutions yet available to public administrations, or to get Free Software or Open Source Software, appropriate for the current needs to be satisfied”.

risulti motivatamente l'impossibilità di accedere a soluzioni già disponibili all'interno della pubblica amministrazione, o a software liberi o a codici sorgente aperto, adeguati alle esigenze da soddisfare”.

The comma 1-ter, among other things, designates the Italian Digital Agency (Agenzia per l'Italia Digitale (AgID) to write modalities and criteria to perform the assessment. To do this the AgID published a news (in Italian) to form a committee (tavolo di lavoro (TdL)) to write guidelines about “Criteri per valutazioni comparative ai sensi dell'art. 68 del CAD”. I found the news curious because there were explicitely written:

“It will be a privileged title holding a role as […] open source software community’s representative”

“Costituirà titolo di preferenza rivestire un ruolo di […] referenti di community del software a codice sorgente aperto”

On December 2012 I sent my application as Java User Group Padua (in Italian)’s representative, on March 2013 I was selected, and in the middle of March I started working at the TdL.

TdL’s activities took place among March and July 2013, by 9 meeting e 5 hearings.

On 8 Jannuary 2014 AgID published (in Italian) AgID published (in Italian) the guidelines by Circolare n. 63/2013 (in Italian).

On the whole I’m almost satisfied. Certainly we might discuss about how these guidelines were or weren’t simple, but undoubtedly they help delineating the path stated by the art. 68. Moreover I’m proud to have participated in defining a national law which rules the country where I live in. I’m also grateful to had the opportunity to live an experience from which I learnt a lot.


Git in Practice book review

This spring I was selected from Manning as one of the technical reviewers of the book “Git in Practice” by Mike McQuaid.

I’ve been using Git for about a year now, and I studied it on the online documentation but I found the McQuaid’s book easier to read because lots of chapters have their title which may be considered as a FAQ and its four subsections Background, Problem, Solution, Discussion, offer a common way to understand the chapter’s main subject.

Commit Messages - Good Practices

Writing good commit messages is extremely important because:

  • good commit messages help the future (poor) maintainer
  • good commit messages speed up the peer reviewing process
  • good commit messages are used to generate a good release note

I hope the presentation “Commit messages - Good practices ” will help developers becoming more aware about how good commit messages could improve their work.

Gradle in Action book review

This autumn I was selected from Manning as one of the technical reviewers of the book “Gradle in Action” by Benjamin Muschko.

Gradle in Action starts with a beautiful introduction to Gradle with the classic “in action” approach.

How to generate DDL with Hibernate 4, Hibernate Tools and Maven

Hibernate Tools is a toolset for Hibernate3 implemented as an integrated suite of Eclipse plugins, together with a unified Ant task for integration into the build cycle.

Working with Maven you can use the hibernate3-maven-plugin (In 2015, Codehaus.org announced that it had come to the end of its life hibernate3-maven-plugin. But this is (as the name states) only for Hibernate 3 and does not support Hibernate 4.

As reported by Thomas Letsch [1] the Hibernate tools for Hibernate 4.x is not yet finished, and the obvious solution is to just use the Maven ant-run plugin and execute the hibernate-tools Ant task. So following the Thomas Letsch’s article I have worked out a solution that suits me well.

Spring in Action Book Review

This summer I red “Spring in Action” by Craig Walls.

The book is well written, easy to read, with lots of code fragments which clarify textual descriptions, and with references to Design Pattern and JSR too.