From: Jason Molenda <jason@molenda.com>
To: scottb@netwinder.org, hjl@lucon.org, nickc@redhat.com,
gdb@sources.redhat.com
Subject: Re: src/ltcf-c.sh
Date: Tue, 05 Sep 2000 19:08:00 -0000 [thread overview]
Message-ID: <20000905190824.A14877@shell17.ba.best.com> (raw)
In-Reply-To: <20000905182042.A7301@shell17.ba.best.com>
I looked into this a bit (after sending my mail note saying there should
be no problem, of course :-). I can reproduce Scott's reported problem.
An update with the an SSH or pserver access methods does not pick
up files added in the src/ directory. I honestly don't know why.
It doesn't have anything to do with the modules file - that file
is only relevant at check-out time; after that, cvs knows nothing
of the module you checked out.
I poked around trying to figure out what is going on this this
directory, but failed (or rather, I have to get back to my real
work :-). For what it's worth, though, this behavior we're seeing
with the top level of the /cvs/src directory is neither expected
nor correct. Something is up with the RCS files here. Or maybe
there is some odd case of cvs that I don't understand and it's
coming up here, but that's not as likely.
As people have suggested, check out binutils/gdb again from the top
level as a workaround.
Jason
next prev parent reply other threads:[~2000-09-05 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-05 18:21 src/ltcf-c.sh Jason Molenda
2000-09-05 19:08 ` Jason Molenda [this message]
2000-09-05 19:20 ` src/ltcf-c.sh Stan Shebs
2000-09-08 0:19 ` src/ltcf-c.sh Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2000-09-08 10:04 src/ltcf-c.sh David Taylor
2000-09-05 11:58 src/ltcf-c.sh Nick Clifton
2000-09-05 14:15 ` src/ltcf-c.sh Scott Bambrough
2000-09-05 14:19 ` src/ltcf-c.sh H . J . Lu
2000-09-05 14:41 ` src/ltcf-c.sh Daniel Berlin
2000-09-06 3:15 ` src/ltcf-c.sh Richard Earnshaw
2000-09-04 18:04 src/ltcf-c.sh Scott Bambrough
2000-09-04 18:11 ` src/ltcf-c.sh H . J . Lu
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=20000905190824.A14877@shell17.ba.best.com \
--to=jason@molenda.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=nickc@redhat.com \
--cc=scottb@netwinder.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 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).