From: Jens Lehmann <Jens.Lehmann@web•de>
To: Gustaf Hendeby <hendeby@isy•liu.se>
Cc: Junio C Hamano <gitster@pobox•com>,
Jacob Helwig <jacob.helwig@gmail•com>,
git@vger•kernel.org
Subject: Re: Unmodified submodules shows up as dirty with 1.6.6.443.gd7346
Date: Mon, 18 Jan 2010 21:50:03 +0100 [thread overview]
Message-ID: <4B54C97B.1050008@web.de> (raw)
In-Reply-To: <7vr5pnqqem.fsf@alter.siamese.dyndns.org>
Am 18.01.2010 18:22, schrieb Junio C Hamano:
> I am suspecting that your "these files ... are named differently on
> different systems" may fall into the same category. Your build may not
> produce "frotz.linux" when compiled on a FreeBSD box (and "frotz.fbsd" on
> a Linux box), but would it hurt more than it helps to list them in the
> same .gitignore to cover both?
If you keep source directories separate from directories for compiler
output you can easily simplify your .gitignore by negating it. So
instead of putting a line into the .gitignore for every file type you
do /not/ want, exclude everything in the build directory and add
exceptions for the files you /do/ want to track.
Then a .gitignore could look like this for building with VC6, VC8 and
Makefile based build systems:
path/to/build/directory/*
!*.dsw
!*.dsp
!*.sln
!*.vcproj
!Makefile
next prev parent reply other threads:[~2010-01-18 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 15:30 Unmodified submodules shows up as dirty with 1.6.6.443.gd7346 Gustaf Hendeby
2010-01-18 16:02 ` Jacob Helwig
2010-01-18 16:54 ` Gustaf Hendeby
2010-01-18 17:14 ` Jacob Helwig
2010-01-18 17:27 ` Gustaf Hendeby
2010-01-18 17:22 ` Junio C Hamano
2010-01-18 20:50 ` Jens Lehmann [this message]
2010-01-19 7:13 ` Johannes Sixt
2010-01-19 8:23 ` Gustaf Hendeby
2010-01-19 14:31 ` Jacob Helwig
2010-01-19 17:29 ` Junio C Hamano
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=4B54C97B.1050008@web.de \
--to=jens.lehmann@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=hendeby@isy$(echo .)liu.se \
--cc=jacob.helwig@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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