git

In the last post, I found that many commits were to the master branch when they should have been on the quarterly branch. Now I think I see why. See this XML: If it’s quarterly, it should name the branch. Case in point: 2020Q4. I went to https://lists.freebsd.org/pipermail/svn-ports-branches/2020-November/thread.html to look for known quarterly commits. Hmm, […]

I need to document this so I can refer to it while debugging. This follows the chain of scripts which processes a commit. Periodic FreshPorts, at present, checks for new commits every three minutes, via this entry in /etc/crontab: That will invoke this script: check_for_git_commits.sh This is a cheat. It touches a file, which is

In my recent post, my conclusion preferred Rename over Delete & Add. Now I’ve changed my mind. I looked at the code, and the database. Now I prefer Delete & Add. The database In the database, there is no way to represent the Rename action without modifying the structure of the commit_log_elements table: The change_type

I spent an evening working through the delete issue with git repos. A Twitter thread was the result. Sergey Kozlov came up with some code changes which changed the XML output. Now I think we have a plan. The commit I’m using for a working example was to editors/nvi2 on 27 Jul 2020 01:58:34 –

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

This is another post in the FreshPorts-git series. Yesterday was good progress. This morning (at Sat Jul 4 13:05:10 UTC 2020) I manually initiated another import of commits from git. It looked like this: This created one XML file for each git commit. The files are dropped into the ~freshports/messages-queues/incoming directory. The freshports-git daemon (well,

I’m documenting this as a go along because I’m sure I’ll be doing something that I later wish I had written down. Create the repo This creates a FreeBSD git-based port repo. echo git clone https://github.com/freebsd/freebsd-ports.git /var/db/freshports/ports-jail/var/db/repos/PORTS-head-git | sudo su -l freshports The latest local commit This tells us the hash of the latest commit

git is coming to FreeBSD. The initial FreshPorts work for git started in September, then was abandoned for unknown reasons. It just fell off the RADAR. This week, it came back to my attention. References Some of the initial research was over Twitter. I’m saving those references here for future reference. The Tweet about the

I was just creating a new jail for working on git & FreshPorts. I was intrigued to see that iocage uses send | receive to create the new jail: [dan@slocum:~] $ ps auwwx | grep iocage root 64166 3.7 0.0 12788 4036 1 D+ 21:16 0:06.10 zfs send system/iocage/releases/12.0-RELEASE/root@git-dev root 64167 2.8 0.0 12752 4036