From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Git Mailing List <git@vger.kernel.org>,
Martin Langhoff <martin@catalyst.net.nz>
Subject: Re: [BUG RFC/PATCH] git-cvsimport
Date: Mon, 16 Aug 2010 17:43:06 +0000 [thread overview]
Message-ID: <AANLkTimXAZMfXWjcb7RKE2_y6_v7MHQRK7oxK42n-5C0@mail.gmail.com> (raw)
In-Reply-To: <7vpqxicyoy.fsf@alter.siamese.dyndns.org>
On Mon, Aug 16, 2010 at 16:25, Junio C Hamano <gitster@pobox.com> wrote:
> Michael Haggerty <mhagger@alum.mit.edu> writes:
>
>> My guess is that cvsps is using CVS commands to access the test CVS
>> repository, and that CVS wants to write to the file CVSROOT/history to
>> log what is being done. The logging behavior can be turned off either:
>> ...
>> Apparently -R and "$CVSREADONLYFS" were added in CVS 1.12.1, which was
>> released in 2003.
>
> That unfortunately does not solve much. t9602 seems to want to create a
> new CVSROOT/val-tags file, so if Ævar wants to keep the source tree
> read-only, the test CVS repository needs to be copied to a scratch place.
>
> Perhaps something like this? I actually have to wonder why cvsIMPORT
> needs to write into anywhere, though.
That looks good. It's pretty much exactly what I was going to submit,
but I was waiting until you applied my other patches to pu (since
they'd with that patch as I changed the setup code in the skip patches
too).
prev parent reply other threads:[~2010-08-16 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 15:33 [BUG RFC/PATCH] git-cvsimport Ævar Arnfjörð Bjarmason
2010-08-14 21:09 ` Jonathan Nieder
2010-08-14 21:39 ` Ævar Arnfjörð Bjarmason
2010-08-16 4:24 ` Michael Haggerty
2010-08-16 16:25 ` Junio C Hamano
2010-08-16 17:43 ` Ævar Arnfjörð Bjarmason [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimXAZMfXWjcb7RKE2_y6_v7MHQRK7oxK42n-5C0@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin@catalyst.net.nz \
--cc=mhagger@alum.mit.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).