From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261524AbVDWJ1d (ORCPT ); Sat, 23 Apr 2005 05:27:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261525AbVDWJ1d (ORCPT ); Sat, 23 Apr 2005 05:27:33 -0400 Received: from postfix4-2.free.fr ([213.228.0.176]:8398 "EHLO postfix4-2.free.fr") by vger.kernel.org with ESMTP id S261524AbVDWJ1c (ORCPT ); Sat, 23 Apr 2005 05:27:32 -0400 Message-ID: <426A14E8.6080005@freehackers.org> Date: Sat, 23 Apr 2005 11:27:04 +0200 From: Philippe Fremy User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Patching / Merging tool X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi For years, I have been willing to write a good patching/merging tool. In my understanding, the kernel is the most patching/merging demanding project and now that bitkeeper is gone, there is a hole to be filled. What would be the requirements for a good patching/merging tool in your opinion ? What are the use cases ? How much of integration is required with the SCM, git in the kernel case ? I am not subscribed, so please CC: me any response. best regards, Philippe