git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hildebrandt <anhi@bioinf.uni-sb.de>
To: git@vger.kernel.org
Subject: How to ignore deleted files
Date: Tue, 11 Mar 2008 13:58:43 +0100	[thread overview]
Message-ID: <47D68203.10905@bioinf.uni-sb.de> (raw)

Dear all,

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)?

Sorry if I overlooked something obvious,

Andreas Hildebrandt

             reply	other threads:[~2008-03-11 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 12:58 Andreas Hildebrandt [this message]
2008-03-11 14:10 ` How to ignore deleted files Jakub Narebski
2008-03-11 14:53   ` Andreas Hildebrandt
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=47D68203.10905@bioinf.uni-sb.de \
    --to=anhi@bioinf.uni-sb.de \
    --cc=git@vger.kernel.org \
    /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).