Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263605AbUDUSuZ (ORCPT ); Wed, 21 Apr 2004 14:50:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263607AbUDUSuZ (ORCPT ); Wed, 21 Apr 2004 14:50:25 -0400 Received: from relay02s.ntr.oleane.net ([194.2.8.83]:63189 "EHLO relay02s.ntr.oleane.net") by vger.kernel.org with ESMTP id S263605AbUDUSuV (ORCPT ); Wed, 21 Apr 2004 14:50:21 -0400 Date: Wed, 21 Apr 2004 20:50:35 +0200 (CEST) From: Marc Herbert X-X-Sender: mherbert@fcat To: linux-kernel@vger.kernel.org Subject: directory "net/core" ignored by bitkeeper :-/ Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 30 Try this in the official 2.4 tree: touch net/ipv4/foo.c touch net/core/bar.c bk extras => net/ipv4/foo.c !!! I am not a bitkeeper wizard, so I can only suggest removing "core" from Bitkeeper/etc/ignore (as opposed to renaming "net/core" :-D) Do many people have "core" files in their developments tree? So often it becomes a major inconvenience? ("major" = more than ignoring net/core) Cheers, Marc. PS: I am not subscribed to the list. Keep me in Cc: if needed. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/