Odd contents of .cvsignore files

Odd contents of .cvsignore files

[Marcus Hall]

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?

Marcus Hall
CorAccess Systems



-------------------------------------------------------
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/

Re: Odd contents of .cvsignore files

[Takashi Iwai]

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


-------------------------------------------------------
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/

Re: Odd contents of .cvsignore files

[Marcus Hall]

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.

Marcus Hall
CorAccess Systems


-------------------------------------------------------
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/

Re: Odd contents of .cvsignore files

[Takashi Iwai]

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/