All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
	Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: arch/powerpc/boot/.gitignore questions
Date: Wed, 10 Sep 2008 14:48:59 -0700	[thread overview]
Message-ID: <48C840CB.6050007@oracle.com> (raw)
In-Reply-To: <48C83FA7.70501@freescale.com>

Scott Wood wrote:
> Randy Dunlap wrote:
>>>> I was looking at the arch/powerpc/boot/.gitignore file.
>>>> Why are all of those non-local-directory files listed there?
>>>> E.g., empty.c, inf*.c, inf*.h, zconf.h, zlib.h, zutil.h, etc.
>>
>> Why would these files be listed in arch/powerpc/boot/.gitignore ??
> 
> Because they're created when building a bootwrapper?
> 
>>>> And what is "dtc"?  I see a dtc-src directory, but "dtc" is MIA.
>>> ./arch/powerpc/boot/dtc
>>
>> Where do you see that?  That's not in 2.6.27-rc6 nor in the current
>> powerpc.git tree.  They both have:
> 
> Of course not -- it wouldn't be in gitignore if it weren't a generated
> file.
> 
>>> pwd
>> /var/linsrc/lin2627-rc6/arch/powerpc/boot
>>> ls -ld dt*
>> drwxr-xr-x 2 rdunlap users 4096 Jul 13 14:51 dtc-src/
>> drwxr-xr-x 2 rdunlap users 4096 Sep  9 19:33 dts/
>>
>>
>> which leads me to believe that the .gitignore entry should be either
>> dts or dtc-src or both, but not "dtc".
> 
> Why would we want to ignore source directories?  dtc is the binary that
> is built from dtc-src.

Thanks.  Got it.

~Randy

      reply	other threads:[~2008-09-10 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 19:24 arch/powerpc/boot/.gitignore questions Randy Dunlap
2008-09-10 20:40 ` Sean MacLennan
2008-09-10 20:49   ` Wolfgang Denk
2008-09-10 20:52     ` Scott Wood
2008-09-10 21:37   ` Randy Dunlap
2008-09-10 21:44     ` Scott Wood
2008-09-10 21:48       ` Randy Dunlap [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=48C840CB.6050007@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.com \
    --cc=smaclennan@pikatech.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.