From: Brendan J Simon <brendan.simon@bigpond.com>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: RfC: Don't cd into subdirs during kbuild
Date: Wed, 09 Oct 2002 10:45:58 +1000 [thread overview]
Message-ID: <3DA37C46.104@bigpond.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210031536370.24570-100000@chaos.physics.uiowa.edu
Kai Germaschewski wrote:
>You must be missing some of the changes (My first push to bkbits was
>incomplete, since I did inadvertently edit Makefile without checking it
>out, I do that mistake all the time...). It's fixed in the current repo.
>
>
Can't bitkeeper be setup to have readonly files for files not checked
out. I know cvs can and other configuration management tools such as
Aegis (which I really like).
Cheers,
Brendan Simon.
prev parent reply other threads:[~2002-10-09 0:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 2:59 RfC: Don't cd into subdirs during kbuild Kai Germaschewski
2002-10-03 3:32 ` Andreas Dilger
2002-10-03 5:18 ` [kbuild-devel] " Peter Samuelson
2002-10-03 14:54 ` Kai Germaschewski
2002-10-03 8:21 ` Xavier Bestel
2002-10-03 14:56 ` Kai Germaschewski
2002-10-03 15:31 ` Xavier Bestel
2002-10-03 20:41 ` Peter Samuelson
2002-10-03 14:05 ` John Levon
2002-10-03 14:27 ` Kai Germaschewski
2002-10-03 14:45 ` John Levon
2002-10-03 19:26 ` Sam Ravnborg
2002-10-03 19:33 ` [kbuild-devel] " Sam Ravnborg
2002-10-03 20:01 ` Sam Ravnborg
2002-10-03 20:19 ` Kai Germaschewski
2002-10-03 20:44 ` Sam Ravnborg
2002-10-03 20:20 ` Peter Samuelson
2002-10-03 20:30 ` Sam Ravnborg
2002-10-03 20:38 ` Kai Germaschewski
2002-10-03 20:50 ` Sam Ravnborg
2002-10-04 19:07 ` Sam Ravnborg
2002-10-04 20:17 ` Sam Ravnborg
2002-10-09 0:45 ` Brendan J Simon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DA37C46.104@bigpond.com \
--to=brendan.simon@bigpond.com \
--cc=kai-germaschewski@uiowa.edu \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.