All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: mhall@coraccess.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Odd contents of .cvsignore files
Date: Sat, 11 Dec 2004 16:31:33 +0100	[thread overview]
Message-ID: <s5hekhwsvfu.wl@alsa2.suse.de> (raw)
In-Reply-To: <20041210205845.GB11880@splunge.coraccess.com>

At Fri, 10 Dec 2004 13:58:45 -0700,
Marcus Hall wrote:
> 
> On Fri, Dec 10, 2004 at 07:01:48PM +0100, Takashi Iwai wrote:
> > At Fri, 10 Dec 2004 10:55:23 -0700,
> > Marcus Hall wrote:
> > > 
> > > I was working with the 1.0.7 release and noticed that some files were
> > > listed in .cvsignore that I found surprising:
> > > 
> > > 	acinclude.m4
> > > 	acore/pcm_lib.c
> > > 	alsa-kernel
> > > 	include/config1.h.in
> > > 	include/linux
> > > 	toplevel.config.in
> > > 
> > > were all listed there.  Is this intentional?
> > 
> > Yes.  They are all dynamically created files.
> > 
> > 
> > Takashi
> 
> That's what I considered at first, but I couldn't find where they were
> generated from.  Of course toplevel.config.in => toplevel.config and
> such, but I didn't see where they otherwise came from.  I also note
> that these (and other, clearly derived files) *are* checked into
> the alsa CVS.

Maybe they are the old files.  Anyway the files are ignored when you
run cvscompile script.  It doesn't matter.

*.c files are created from *.patch files.
Others are usually in alsa-driver/Makefile.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

      reply	other threads:[~2004-12-11 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 17:55 Odd contents of .cvsignore files Marcus Hall
2004-12-10 18:01 ` Takashi Iwai
2004-12-10 20:58   ` Marcus Hall
2004-12-11 15:31     ` Takashi Iwai [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=s5hekhwsvfu.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mhall@coraccess.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.