On Wed, Aug 03, 2011 at 01:11:48AM -0700, Tomas M wrote: > I think that git offers much more functionality than anybody needs. > > My guess is that it is unpleasant for people to download entire git > tree for Linux kernel, because > 1) they already have some kernel sources unpacked somewhere in /usr/src/linux* > 2) the git tree is really HUGE to download, since it includes much > more data than just the kernel sources (if I understand it right). > > In my opinion, average user wants to download AUFS just as a patch for > his particular kernel version. That may be the reason why people prefer to > use the standalone version of aufs.
The thing is that you don't need to re-download the entire git tree every new release, you can just use what you have and pull the differences. My use is: - Clone the kernel git tree - Add aufs as a remote branch - every new kernel Z release (X.y.z) I pull kernel tree - every new aufs release I pull aufs remote branch It is very easy. And when a new Y release is released I clone this entire tree and apply steps above. It is insane do download every Z release tarball and apply aufs, git makes life easier. That's my opinion Best Regards -- Bruno > > > Tomas M > > > > > On Tue, Aug 2, 2011 at 9:47 AM, <sf...@users.sourceforge.net> wrote: > > > > A few months before, I've posted a message "[RFC] aufs2.2 will support > > v2.6.36 and later". But I change my mind and am going to make aufs2.2 > > support v2.6.35 - v2.6.39, since v2.6.35 is listed as long-term support > > kernel on www.kernel.org now. > > In the future, aufs2.3 will be for v2.6.38 - 2.6.39 for example, and > > finally aufs2 will end when the support for 2.6.39 ends. > > > > For v3.0 and later, I will make a new GIT repo aufs3-linux.git, > > aufs3-standalone.git and aufs-util.git. > > > > The aufs3-linux.git repo is a successor of aufs2-2.6.git, and will be a > > clone of git://git.kernel.org/.../torvalds/linux.git (mainline) plus > > "aufs3.0" and "aufs3.x-rcN" branches. Of course when linux-3.1 is > > release, a new branch "aufs3.1" will be created. > > Note that "aufs3.x-rcN" is for latest -rcN kernel and its branch name > > will not change. > > In this scheme, the git commit id will be important to identify the > > aufs version. This is essentially equivalent to current scheme. > > > > The aufs3-standalone.git repo is a successor of aufs2-standalone.git, > > and will have the aufs files only (without the full kernel source > > files). There will be the similar branches, > > aufs3.0, aufs3.1 ... aufs3.x-rcN. > > The date in the aufs version string will be held in order to identify > > the aufs version. > > > > The aufs-util.git repo is a successor of aufs2-util.git, but there is no > > "3" in its name. The branch name will be aufs3.0, aufs3.5, ie. when the > > utiltilies are equivalent to the previous version, the branch will not > > be created. So if you use aufs3.1 for linux-3.1 and the aufs3.1 branch > > does not exist in this repo, then you should use aufs3.0. > > > > Currently I think all these new GIT repo will be placed SourceForge.net. > > For years, Bruno Cesar Ribas and Luis Carlos Erpen de Bona, C3SL (the > > Center for Scientific Computing and Free Software, Federal University of > > Parana, Brazil) served the public aufs GIT repo. > > Thanks again. > > > > I may NOT create aufs3-linux.git repo since most users seem to be using > > the standalone version. I have received several mails complaning > > "downloading (git-clone) aufs took too long time and the size is incredibly > > large" from ignorant and innocent people. I guess they are simply new to > > aufs GIT repo. In other words, > > - new users try aufs2-2.6.git, and meet some unplesant situation. > > - advanced users use aufs2-standalone.git. > > (just my guess) > > In order to save new users, it may be better that I won't provide > > aufs3-linux.git. But GIT has a strong and useful features to merge > > files. I am not decided yet. > > > > Also git-log for the current aufs2-standalone.git is not very useful > > because the commits in aufs2-standalone.git is extracted from > > aufs2-2.6.git and merged manually. I don't like this approache. > > > > Anyway, if you have any option, please post and let me know. > > > > > > J. R. Okajima > > > > ------------------------------------------------------------------------------ > > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > > The must-attend event for mobile developers. Connect with experts. > > Get tools for creating Super Apps. See the latest technologies. > > Sessions, hands-on labs, demos & much more. Register early & save! > > http://p.sf.net/sfu/rim-blackberry-1 > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 -- Bruno Ribas - ri...@inf.ufpr.br http://www.inf.ufpr.br/ribas ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1
