public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: sid@sourceware.org
Subject: Re: Does sid use the src/blt directory?
Date: Wed, 05 Apr 2006 16:07:00 -0000	[thread overview]
Message-ID: <20060405160510.GD16498@redhat.com> (raw)
In-Reply-To: <200604051601.JAA09307@hpsje.cup.hp.com>

On Wed, Apr 05, 2006 at 09:01:49AM -0700, Steve Ellcey wrote:

> I have been looking into whether or not the src/blt, src/iwidgets, and
> src/mmalloc directories in the source tree could be removed.  [...]

I know of no current or recent use of BLT in sid.  Even if there was,
using a system blt instead of a colocated source one would be
acceptable.  So, IMO you can go ahead with the clean up, thanks!

- FChE

      reply	other threads:[~2006-04-05 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 16:01 Steve Ellcey
2006-04-05 16:07 ` Frank Ch. Eigler [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=20060405160510.GD16498@redhat.com \
    --to=fche@redhat.com \
    --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).