linux-kernel - Re: Linux 3.0-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110531054008.GA1906@mako-laptop>
Date:	Tue, 31 May 2011 07:40:08 +0200
From:	Mariusz Kozlowski <mk@....zgora.pl>
To:	david@...g.hm
Cc:	Mariusz Kozlowski <mk@....zgora.pl>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.0-rc1

On Mon, May 30, 2011 at 03:48:49PM -0700, david@...g.hm wrote:
> >You could consider freezing linux-2.6.git repository and creating new
> >linux-3.git repository that would serve for a couple of years until
> >linux-4.git. At the same time development history could be dropped between
> >trees so that inital clones are lighter. Anyone interested in history
> >can download idx/pack from linux-2.6.git repo and attach it using gratf
> >point[1] anyway.
> >
> >Pros:
> >- obvious naming scheme wrt repository contents
> >- smaller initial clone
> >- new clean tag namespace
> >
> >Cons:
> >- broken bisection for some time
> >- impaired log/blame/whatchanged and friends
> 
> in addition won't there be problems merging in work done on the old
> tree? (since there would be no common history)

Everyone would need to restart and probably reapply they changes on top
of new tree (because of lack of common history).

> everyone would need to re-clone their repository (and attaching
> history wouldn't help this)
> 
> there are probably others.
> 
> frankly I don't see any real benifits from the Pros you list. the
> initial clone is already rather small, it probably won't make that
> big a difference to throw away several years of history.

linux-2.6.git is all about lots of small changes so size isn't all that
big today but there are quite many objects. Using grafts might help
decreasing size of repository. I just mentioned it because it is a bit
of a revolution time anyway and otherwise current tree will grow for next
decade or so.

It's just an idea, I'm happy either way.

Thanks.
-- 
Mariusz Kozlowski
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/