From: Andreas Hildebrandt <anhi@bioinf.uni-sb.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to ignore deleted files
Date: Tue, 11 Mar 2008 15:53:20 +0100 [thread overview]
Message-ID: <47D69CE0.3030505@bioinf.uni-sb.de> (raw)
In-Reply-To: <m3y78pxsf5.fsf@localhost.localdomain>
Dear Jakub!
Jakub Narebski schrieb:
>> our git repository contains a number of .tar.gz - files that are
>> automatically extracted and then deleted during the build process.
>> Unfortunately, commiting any changes after that step will mark those
>> files as deleted and try to commit that to the repository. Is there any
>> way to tell git to ignore those files automatically (apart from changing
>> our build process not to use or not to delete those files)?
>>
>
> I don't quite understand: are those .tar.gz files stored in _source_
> repository? That would be a bit strange...
>
>
I absolutetly agree that it's strange. The main reason for this is that
we have some collections of data files (some of them pretty large) that
can be compressed pretty effectively. At compilation time, it is decided
if the files are needed or not. If so, they are extracted. In the end,
the .tar.gz files are deleted since they are no longer needed. In
addition, once a user obtained a checkout, the whole thing is supposed
to work without a further net connection, so downloading the files
during build is not really an option.
> I guess that you have tried adding "*.tar.gz" to either .gitignore or
> .git/info/excludes file?
>
I did, but as far as I understand it, these only work for untracked
files, and the files themselves are tracked (from time to time, they
change and the idea was to track those changes). Or am I missing
something here?
btw: I just noted that
git-commit $(git-ls-files -m --exclude-from=.git/info/exclude)
with the correct entries in the exclude file seems to do pretty much
what I want it to do, namely finding all modifications apart from those
mentioned in the exclude file and commiting them. Would this be a sane
strategy to handle things before we can maybe some day re-structure our
build process?
Thanks a lot for your help!
Andreas Hildebrandt
next prev parent reply other threads:[~2008-03-11 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 12:58 How to ignore deleted files Andreas Hildebrandt
2008-03-11 14:10 ` Jakub Narebski
2008-03-11 14:53 ` Andreas Hildebrandt [this message]
2008-03-11 15:07 ` Santi Béjar
2008-03-11 18:03 ` Git and pristine-tar Sergio Callegari
2008-03-11 15:43 ` How to ignore deleted files David Tweed
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=47D69CE0.3030505@bioinf.uni-sb.de \
--to=anhi@bioinf.uni-sb.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).