[Pkg-scicomp-devel] Migrating some repositories to Git

Rafael Laboissiere rafael at debian.org
Fri May 1 12:20:31 UTC 2009

* Rafael Laboissiere <rafael at debian.org> [2009-05-01 12:13]:

> * Christophe Prud'homme <prudhomm at debian.org> [2009-05-01 07:32]:
> > no objection at all
> Okay, I am going to migrate abinit, openmx, and paraview.  Ondrej, is there
> anything special that should be done in the git repository for using
> git-buildpackage?  See, for instance, the glpk repo [1].  I tag each Debian
> release with the package version number (e.g. 4.37-2).  Is the convention
> for git-buildpackage different (e.g. prepending "debian/" to the tag)?

I went ahead and migrated this three packages.  Only paraview had SVN tags
and I used the Debian version number for tagging the appropriate commits.
It is easy to change the tags later, so I pushed already the whole thing.

Take a look at:

and tell if it is okay with you.  After that, I will remove the SVN

As regards the old SVN commits for these packages, I have noticed some
things and would suggest you to do the following in the future:

1. Do not lump several changes in a single commit.  If it is possible, break
   down your changes into smaller commits, each one related to a single
   improvement or a single bug fix.  The "git add -i" command will be
   your friend here.

2. When writing commit messages, try to write a single, self-contained
   sentence in the first line that summarize the commit.  Think at
   something like a Subject for an email message.  If the commit needs
   more explanation, skip a blank line and add one or more paragraphs
   with a detailed description.  I found a very funny commit message in
   the abinit repo [1]:


       what about those opt flags?

   [1] http://git.debian.org/?p=pkg-scicomp/abinit.git;a=commit;h=87a82af66c119e60e2b9e189939287132c5c95e7


More information about the Pkg-scicomp-devel mailing list