Make sure the "Commit Range" option is selected. To do so, simply press Push.Once the move from Subversion to Git occurs, it will be difficult for your changes to local checkouts of the SVN trunk to be transitioned into Git. Creating Trunk, Branches, and Tags Folders in an SVN Repository In the SVN Repository views SVN Repositories section, right-click on the repository location. However, you can make it much easier by committing your changes to a personal branch of the Subversion repository prior to the transition. This is the easiest process for getting your changes transitioned to Git. I suggest something descriptive like "SVN_to_GIT_branch_kavulich" svn copy -m 'Creating branch for Git transition' Follow the steps below to create a new branch that contains your changes:Ĭreate a new branch using svn copy. NOTE: If your changes are based on a much older version of the trunk, you may want to create your branch from the same revision number as your current revision. You can find your revision number with "svn info". cd /Users/kavulich/my_changes/trunk svn status M Registry/registry.var M inc/version_decl svn copy -r8350 -m 'Creating branch for Git transition based off revision number 8350 of the trunk' Įnter the directory which is your local copy of the SVN trunk with the changes you wish to save. I’m following Subversion best practices for my project directory structure, using trunk, tags and branches sub-directories. Use the "svn switch" command to convert your local "trunk" copy into a copy of this new branch. Right-click on the local repository workspace folder in Windows Explorer and pick TortoiseSVN -> Branch/tag from the Context menu. This post documents my recent experiments with Oleksandr Tymoshenko’s patches to get the FreeBSD 10-CURRENT kernel running in a Qemu-emulated Versatile Platform Board (VersatilePB) armv6 environment. I’ve been looking for a way to build packages for FreeBSD running on small ARM devices (e.g. the NS-K330 with 32MB RAM), and recently stumbled across Oleksandr Tymoshenko’s work here. He has developed patches enabling the FreeBSD 10-CURRENT kernel to be built for the Versatile Platform Board (VersatilePB) under Qemu. Oleksandr notes that his patch creates a kernel that is “ …fully compatible with Raspberry Pi’s userland, or Pandaboard’s one. On December 9th I updated my FreeBSD src tree to svn version r244046: nsk330-builder# cd /src So you can use latest RPi SD card image.” Using the RPi SD card userland image provided here I can create an armv6 environment within which to build ARM packages for other devices that are too small to build Ports themselves. Grabbed a copy of the patch from here, stored it as ~gja/versatilepb.diff and applied it: nsk330-builder# patch /* 128MB */ Now create a new directory for the VersatilePB files: nsk330-builder# cd. # Uncomment following lines for framebuffer/syscons supportĭownloaded the kernel build script from here, stored it as ~gja/build-versatile.sh, edited SRCROOT and MAKEOBJDIRPREFIX inside the script to point to /src/ and /usr/obj/ respectively, then ran it: nsk330-builder# ~gja/build-versatile.sh The resulting image file is stored at /src/sys/freebsd-versatilepb.flashĪlthough Oleksandr recommends Qemu 1.3.0, I got reasonable success using Qemu 1.1.1 (the latest current version in FreeBSD’s Ports collection under qemu-devel). Started qemu’s ARM emulator (qemu-system-arm) with GUI to show the console: % qemu-system-arm -M versatilepb -m 256M -kernel freebsd-versatilepb.flash -cpu arm1176 -hda freebsd-pi-r243778.img -net nic -net tapĪudio: Failed to create voice `lm4549.out' I retrieved and uncompressed this RPi SD card image to provide a World for my VersatilePB kernel (Note: The uncompressed freebsd-pi-r243778.img file is ~1GB.) There were random freezes during heavy load, but still workable enough to prove the FreeBSD kernel will run under Qemu/VersatilePB. “ dmesg -a” confirmed that the kernel recognises 256MB of available RAM. With tap-based network support on the host, qemu is able to offer network access to the FreeBSD guest. Running “ dhclient smc0” results in correct assignment of a DHCP address from my local LAN space, and I was then able to adduser a new local user and ssh into the VersatilePB FreeBSD VM from elsewhere on my home network.Ĭonsole log from a similar boot on December 14th shows how the VM appears to the new kernel: # more /var/log/messagesĭec 2 21:52:52 raspberry-pi newsyslog: logfile first createdĭec 14 09:34:39 raspberry-pi syslogd: kernel boot file is /kernelĭec 14 09:34:39 raspberry-pi kernel: KDB: debugger backends: ddbĭec 14 09:34:39 raspberry-pi kernel: KDB: current backend: ddbĭec 14 09:34:39 raspberry-pi kernel: Copyright (c) 1992-2012 The FreeBSD Project.ĭec 14 09:34:39 raspberry-pi kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994ĭec 14 09:34:39 raspberry-pi kernel: The Regents of the University of California.
0 Comments
Leave a Reply. |