From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Helmut Hullen" Subject: Re: version Date: 21 Jan 2011 16:19:00 +0100 Message-ID: References: <20110121151240.GB811@carfax.org.uk> Reply-To: helmut@hullen.de Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: linux-btrfs@vger.kernel.org Return-path: In-Reply-To: <20110121151240.GB811@carfax.org.uk> List-ID: Hallo, Hugo, Du meintest am 21.01.11: >>> Check the wiki, I keep that updated: >>> https://btrfs.wiki.kernel.org/index.php/Main_Page#News >> >> Thank you - that's more simple for me than first cloning via "git >> clone" and then running "git log". > Once you've done a git clone, you can keep it up to date by > running "git pull". This is pretty efficient, and will only transfer > the changes since the last time you retrieved it. That's true (surely!). But my major interest is only to run btrfs (without those nasty problems like ENOSPC), not to develop it. For developping I've enough other playing grounds (too much ...). > Sadly, it won't help you with reading the output of "git log". :) That's a minor problem - just 3 minutes to find the way git wants. Viele Gruesse! Helmut