linux-kernel - Re: merging other repos into linux-2.6

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: <alpine.LFD.2.00.0810301843220.21084@nehalem.linux-foundation.org>
Date:	Thu, 30 Oct 2008 18:47:56 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"J.R. Mauro" <jrm8005@...il.com>
cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: merging other repos into linux-2.6

On Thu, 30 Oct 2008, J.R. Mauro wrote:
> 
> But if this is as hard to do properly as Linus says, I would be wary of 
> the precedent merging in their history might set. Suddenly we could have 
> tons of developers clamoring for the same treatment.

I don't think it's _hard_. But I think it does require some effort. 

Quite frankly, if it comes from CVS, I expect the logs, for example, to be 
totally inappropriate. I've never ever seen a CVS project that has sane 
commit messages (ok, so they're not "commits" in CVS, but you know what I 
mean).

That's just one example. I'm not willing to pull history if it's full of 
crap. Pulling history for "history's sake" is worthless. The end result 
has to actually be meaningful and help _future_. 

So I strongly suspect that an "automated" history merge is simply not 
appropriate, and almost certainly results in an end result that is not up 
to snuff. And the question is whether anybody is willing to actually put 
in the effort to make the history actually be useful.

		Linus
--
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/