From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Add .gitignore files
Date: Mon, 26 Feb 2007 10:58:49 -0600 [thread overview]
Message-ID: <45E311C9.4060905@freescale.com> (raw)
In-Reply-To: <20070226131538.EF5E9352674@atlas.denx.de>
Wolfgang Denk wrote:
> I never felt the need for a .gitignore file; mayby you can explain
> what you need it for?
To keep the output of git-status clean. I need to do a "make clean" in order
for git-status to give me meaningful results.
Another reason for .gitignore is to avoid accidentally including target files in
a patch.
> -> cg-status
> ...
> ? LOG/
> ? board/amcc/yellowstone/
> -> git-ls-files --others
> LOG/cam5200.ERR
> LOG/cam5200.MAKELOG
> ->
>
> The first command shows me that there is a stale (empty) directory
> left, the second doesn't.
Hmmm... git-status doesn't show the LOG directory either.
If git-ls-files were updated to include empty directories, would you be willing
to have .gitignore files?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-26 16:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 23:26 [U-Boot-Users] [PATCH] Add .gitignore files Timur Tabi
2007-02-20 23:47 ` Grant Likely
2007-02-26 13:15 ` Wolfgang Denk
2007-02-26 16:58 ` Timur Tabi [this message]
2007-02-26 21:38 ` Wolfgang Denk
2007-02-26 21:46 ` Timur Tabi
2007-02-26 22:00 ` Jerry Van Baren
2007-02-27 0:35 ` Grant Likely
2007-02-27 1:19 ` Andy Fleming
2007-02-27 1:25 ` Wolfgang Denk
2007-02-27 1:40 ` Andy Fleming
2007-02-27 6:42 ` Grant Likely
2007-02-27 7:01 ` Stefan Roese
2007-02-27 7:15 ` Grant Likely
2007-02-27 7:33 ` Stefan Roese
2007-02-27 7:42 ` Grant Likely
2007-02-27 14:56 ` Timur Tabi
2007-02-27 15:48 ` Kumar Gala
2007-02-27 22:30 ` Haavard Skinnemoen
2007-02-26 17:54 ` Scott Wood
2007-02-26 13:11 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2007-09-05 14:01 Grant Likely
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=45E311C9.4060905@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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.