subversion vs git – in the database

I want to document some of the not-visible differences between a git commit and a subversion commit when in the database.

subversion git
id 808224 808303
message_id 202007091812.069IC6QK044004@repo.freebsd.org a1d2d5b40fba4186daf29b2b2e9ff2dd8b7d8039
message_date 2020-07-09 18:12:06+00 2020-07-09 18:12:06+00
message_subject svn commit: r541803 – in head/devel: . py-absl-py [null]
date_added 2020-07-09 18:39:53.510006+00 2020-07-09 18:59:49.863092+00
commit_date 2020-07-09 18:12:06+00 2020-07-09 18:12:06+00
committer sunpoet sunpoet
description Add py-absl-py 0.9.0

Abseil Python Common Libraries is a collection of Python library code for
building Python applications. The code is collected from Google’s own Python
code base, and has been extensively tested and used in production.

Features:
– Simple application startup
– Distributed commandline flags system
– Custom logging module with additional features
– Testing utilities

WWW: https://github.com/abseil/abseil-py

Add py-absl-py 0.9.0

Abseil Python Common Libraries is a collection of Python library code for
building Python applications. The code is collected from Google’s own Python
code base, and has been extensively tested and used in production.

Features:
– Simple application startup
– Distributed commandline flags system
– Custom logging module with additional features
– Testing utilities

WWW: https://github.com/abseil/abseil-py

system_id 1 1
encoding_losses f f
svn_revision 541803 f2bfe60090b840b6d99a3288c0b745843cefcfe1
repo_id 1 [null]

Of note:

  1. message_id – In subversion, I’ve used the email message_id of the incoming commit. In git, it is the commit hash
  2. message_subject – The message subject is taken from the subversion email commit message. There is no such field for git because we are extracting directly from git.
  3. svn_revision – These are the subversion revision number and the git commit hash, respectively.
  4. repo_id – This is null for git, and I am not sure why. This may need to be fixed.
Website Pin Facebook Twitter Myspace Friendfeed Technorati del.icio.us Digg Google StumbleUpon Premium Responsive

Leave a Comment

Scroll to Top