From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <sje@cup.hp.com>
Cc: dave.korn@artimi.com, binutils@sourceware.org,
gdb@sourceware.org, insight@sourceware.org, sid@sourceware.org
Subject: Re: Patch: Remove src/blt, src/iwidgets, src/mmalloc directories
Date: Thu, 20 Apr 2006 16:35:00 -0000 [thread overview]
Message-ID: <20060420163544.GA18205@nevyn.them.org> (raw)
In-Reply-To: <200604201628.JAA07981@hpsje.cup.hp.com>
On Thu, Apr 20, 2006 at 09:28:54AM -0700, Steve Ellcey wrote:
> > BTW, do you need to check over the CVSROOT files and make sure these dirs
> > aren't still referenced by e.g. 'modules' or any of the other administrative
> > files?
Removing them breaks checking out old versions, sometimes. But for
these particular directories I'm inclined to agree. Please leave the
version in old-gdb.
> This certainly seems like a good idea but, not being a CVS expert, I am
> not sure how to do it. Where are these CVSROOT files? I don't see them
> in my checked out src tree or in the web based src tree viewer. Can
> they be seen without logging on to sourceware.org? If not, then I don't
> think that I can check them since I don't think CVS write permission
> comes with sourceware.org login permission.
Check out the module "CVSROOT" from the same path you check out src.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-20 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 15:24 Steve Ellcey
2006-04-20 16:00 ` Dave Korn
2006-04-20 16:29 ` Steve Ellcey
2006-04-20 16:35 ` Daniel Jacobowitz [this message]
2006-04-20 16:36 ` Dave Korn
2006-04-25 19:46 ` Steve Ellcey
2006-04-25 19:56 ` Daniel Jacobowitz
2006-04-25 20:02 ` Steve Ellcey
2006-05-04 15:12 ` Daniel Jacobowitz
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=20060420163544.GA18205@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=dave.korn@artimi.com \
--cc=gdb@sourceware.org \
--cc=insight@sourceware.org \
--cc=sid@sourceware.org \
--cc=sje@cup.hp.com \
/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).