Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>,
	Nathanael Nerode <neroden@twcny.rr.com>,
	gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com, dj@redhat.com
Subject: Re: (top level patch) Autoconfiscate. (Woo!)
Date: Sat, 28 Dec 2002 10:08:00 -0000	[thread overview]
Message-ID: <20021228180647.GA18127@nevyn.them.org> (raw)
In-Reply-To: <orznqq3tz2.fsf@free.redhat.lsd.ic.unicamp.br>

On Sat, Dec 28, 2002 at 03:59:29PM -0200, Alexandre Oliva wrote:
> On Dec 28, 2002, Alexandre Oliva <aoliva@redhat.com> wrote:
> 
> >> P.S. Why is Makefile.tpl not included in the src CVS tree?  It is
> >> included in the gcc CVS tree.
> 
> > It should be there too.  Probably just a pilot error.
> 
> Hey, wait!  It *is* there.  Perhaps you didn't check out the module
> file again, so you don't have it?  Files in the top level directory
> are special, in a certain way.  You don't get them when you just
> update.

Maybe you don't.  I always do.  CVS has no idea of a toplevel directory
(or if it does, it doesn't matter here, since src/ is not the toplevel
directory of the repository, but the second level).

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-28 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 20:03 Nathanael Nerode
2002-12-27 23:07 ` Alexandre Oliva
2002-12-28  7:06 ` Mark Kettenis
2002-12-28  8:24   ` Alexandre Oliva
2002-12-28 10:05     ` Alexandre Oliva
2002-12-28 10:08       ` Daniel Jacobowitz [this message]
2002-12-28 10:34         ` Alexandre Oliva
2002-12-27 23:23 Nathanael Nerode

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=20021228180647.GA18127@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=neroden@twcny.rr.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