On 02/16/2010 07:55 PM, maximilian attems wrote:
hello Kir, nice to see your message. on unrelated note: ~/src/linux-2.6.26-openvz$ git pull git.openvz.org[0: 64.131.90.162]: errno=Connection refused fatal: unable to connect a socket (Connection refused) online I see no change since, so doesn't matter that much. On Thu, 11 Feb 2010, Kir Kolyshkin wrote:Thanks for the info. We have discussed this at length and the resolution is we are all for it. This means we will try hard to do a rebase as soon as possible, and I hope we will succeed. If (or whenever you will) know the exact deadline date (or any close approximation), please let us know, this is important.the freeze was scheduled for March, but is delayed. The sooner you have a tree I could clone from and have a patch from the better.
We now have the tree which is more or less working (with some known and unknown bugs). It is available as git: git://git.openvz.org/pub/linux-2.6.32-openvz http://git.openvz.org/pub/linux-2.6.32-openvz gitweb: http://git.openvz.org/?p=linux-2.6.32-openvz;a=summary
Also, can you please point us to the location of the git repository of what will become the linux kernel for the next debian release? I checked git.debian.org but where there are too many kernels to look at. If it is not in git then when it is?It is due to legacy reasons (bitkeeper was in usage back then) in svn and also out of legacy reasons has all patches in debian/patches. if you want a git copy from current git svn clone I can easily tar it up.
Has anything changed since then? Do we get the Debian kernel from svn?Another question -- in what form do you like to see our work -- i.e. git tree,
set of patches applicable to your kernel, anything else?
git usage is planed post squeeze to settle with procedures. amicalement maks