Re: [fpc-other] GIT versioning server on Raspberry Pi?
On 30/05/17 14:30, Graeme Geldenhuys wrote: On 2017-05-29 13:01, Mark Morgan Lloyd wrote:> I'd use something like an HP> Microserver with at least mirrored discs, Yes the HP Microservers are excellent! I highly recommend them, and they are cheap as chips - so a real bargain. I would load it with good NAT/Server style disks (eg: Western Digital Red disks) and a small SSD boot disk (or even a USB stick). Run FreeBSD or Linux with ZFS in RAID-z1 or RAID-z2. Like I said is some other thread, I wouldn't trust my data on any other file system again - only ZFS for me! A all-in-one easy to set up system is FreeNAS (which comes standard with ZFS) and includes other since things like easy directory sharing via FTP, HTTP, NFS etc. All managed via a simple web interface. It appears that ZFS is also available for Debian "Stretch", and is in "Jessie" backports. That's the original Sun implementation, via BSD. It would almost certainly need more than an RPi to do it justice though. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] ___ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other
Re: [fpc-other] GIT versioning server on Raspberry Pi?
On 2017-06-04 23:12, Bo Berglund wrote: Why is the repo in this condition? And what to do about it? Obviously going over it with git reset HEAD ... isn't really practical since this example project (an Android App) contains deeply nested folder trees with hundreds of files. Like I said, I have no experience with CVS or covertions from CVS-to-Git. 1) I suggest you start with a 'gitk --all' and see how the history of your repository looks like, and if there is any history at all. 2) You don't have to reset each file one by one. You can do it all in one go with: git reset --hard But why all your files are marked for deletion is a mystery to me. 3) This is never mentioned in ANY repository conversion guides, but something I ALWAYS do. After you ran your automated migration to Git, I would use a comparison tool (eg: Beyond Compare) and compare a _clean_ original repository against the newly migrated Git repository. Do a new checkout of the original repository (CVS, Subversion etc) to make sure it is clean and you know it is the latest code from the server. Technically there should be NO differences, but on the small chance that there is, now is the time to see the differences and commit those into Git so you know going forward both repositories have the exact same state (at the time of migration). Regards, Graeme -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp ___ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other
Re: [fpc-other] GIT versioning server on Raspberry Pi?
On 04/06/17 23:12, Bo Berglund wrote: > Report on progress: > I have found a way to convert CVS to GIT using the cvs2svn module, > which contains a cvs2git file. It was described in this article: > https://devsector.wordpress.com/2014/05/17/migrate-cvs-to-git-with-cvs2svn/ > [...] > > I am worrying that I am doing this all wrong... > > It is possible to clone the repo and get the expected file tree out, > though. > You have (probably) created the repo in 'bare' mode (no checked out working copy?) (or the conversion process does it inadvertently) When you clone, you get the working directory, then you'd need to push changes to bare repo (just like you would on SVN or CVS by default) (hope it's that, idk because I don't use bare repos). -L. ___ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other
