From: "Santi Béjar" <sbejar@gmail.com>
To: "Andreas Hildebrandt" <anhi@bioinf.uni-sb.de>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: How to ignore deleted files
Date: Tue, 11 Mar 2008 16:07:13 +0100 [thread overview]
Message-ID: <8aa486160803110807m277363d6kaf7e1dd401fc9e2f@mail.gmail.com> (raw)
In-Reply-To: <47D69CE0.3030505@bioinf.uni-sb.de>
On Tue, Mar 11, 2008 at 3:53 PM, Andreas Hildebrandt
<anhi@bioinf.uni-sb.de> wrote:
>
> 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.
Maybe you can have a look to pristine-tar. From:
http://kitenet.net/~joey/code/pristine-tar/
pristine-tar can regenerate a pristine upstream tarball using only a
small binary delta file and a copy of the source which can be a
revision control checkout.
The package also includes a pristine-gz command, which can regenerate
a pristine .gz file.
The delta file is designed to be checked into revision control
along-side the source code, thus allowing the original tarball to be
extracted from revision control.
---------------------
So you can recreate the tar from files in a git branch.
Santi
next prev parent reply other threads:[~2008-03-11 15:08 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
2008-03-11 15:07 ` Santi Béjar [this message]
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=8aa486160803110807m277363d6kaf7e1dd401fc9e2f@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=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).