From: Pete Wyckoff <pw@padd.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Fwd: Git and Large Binaries: A Proposed Solution
Date: Sun, 23 Jan 2011 09:14:17 -0500 [thread overview]
Message-ID: <20110123141417.GA6133@mew.padd.com> (raw)
In-Reply-To: <20110121222440.GA1837@sigill.intra.peff.net>
peff@peff.net wrote on Fri, 21 Jan 2011 17:24 -0500:
> cat >$HOME/local/bin/huge-clean <<'EOF'
> #!/bin/sh
>
> # In an ideal world, we could actually
> # access the original file directly instead of
> # having to cat it to a new file.
> temp="$(git rev-parse --git-dir)"/huge.$$
> cat >"$temp"
Just a quick aside. Since (a2b665d, 2011-01-05) you can provide
the filename as an argument to the filter script:
git config --global filter.huge.clean huge-clean %f
then use it in place:
$ cat >huge-clean
#!/bin/sh
f="$1"
echo orig file is "$f" >&2
sha1=`sha1sum "$f" | cut -d' ' -f1`
cp "$f" /tmp/big_storage/$sha1
rm -f "$f"
echo $sha1
-- Pete
next prev parent reply other threads:[~2011-01-23 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin=UySutWLS0Y7OmuvkE=T=+YB8G8aUCxLH=GKa@mail.gmail.com>
2011-01-21 18:57 ` Fwd: Git and Large Binaries: A Proposed Solution Eric Montellese
2011-01-21 21:36 ` Wesley J. Landaker
2011-01-21 22:00 ` Eric Montellese
2011-01-21 22:24 ` Jeff King
2011-01-21 23:15 ` Eric Montellese
2011-01-22 3:05 ` Sverre Rabbelier
2011-01-23 14:14 ` Pete Wyckoff [this message]
2011-01-26 3:42 ` Scott Chacon
2011-01-26 16:23 ` Eric Montellese
2011-01-26 17:42 ` Joey Hess
2011-01-26 21:40 ` Jakub Narebski
2011-03-10 21:02 ` Alexander Miseler
2011-03-10 22:24 ` Jeff King
2011-03-13 1:53 ` Eric Montellese
2011-03-13 2:52 ` Jeff King
2011-03-13 19:33 ` Alexander Miseler
2011-03-14 19:32 ` Jeff King
2011-03-16 0:35 ` Eric Montellese
2011-03-16 14:40 ` Nguyen Thai Ngoc Duy
2011-01-22 0:07 ` Joey Hess
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110123141417.GA6133@mew.padd.com \
--to=pw@padd.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).