From: jidanni@jidanni.org
To: peff@peff.net, Johannes.Schindelin@gmx.de
Cc: nico@cam.org, gitster@pobox.com, mdl123@verizon.net,
spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-bundle.txt: Dumping contents of any bundle
Date: Fri, 02 Jan 2009 06:12:56 +0800 [thread overview]
Message-ID: <87fxk2u13r.fsf@jidanni.org> (raw)
In-Reply-To: 20090101192153.GA6536@coredump.intra.peff.net
JK> Maybe it would be worth adding an option to dump the uncompressed
JK> deltas to a file or directory so you could run "strings" on them
JK> to recover some of the data.
I got as far as these wheezy little bytes,
$ ls ??/*|tr -d /|sed q|xargs git cat-file tree|perl -pwe 's/[^\0]+[\0]//'|hd
00000000 ae 83 2f 22 45 89 2d dd e5 22 13 57 46 64 48 b4 |../"E.-..".WFdH.|
00000010 09 77 51 42 |.wQB|
before I ran out of tools to crack it. It must be in some standard git
gzip format. There should be a command line tool to crack it with
provided in the git suite.
Anyways, one day some forensics department will need to crack one of
these things, and I want the instructions available.
JS> Just for the record: this is in so many ways not a commit message I want
JS> to have in git.git. I hope it is not applied.
Is that where they end up? Oops, please reword it for me, anybody.
next prev parent reply other threads:[~2009-01-01 22:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:29 How to extract files out of a "git bundle", no matter what? jidanni
2008-12-19 19:32 ` Shawn O. Pearce
2008-12-19 19:57 ` Mark Levedahl
2008-12-19 20:13 ` jidanni
2008-12-19 20:21 ` Jeff King
2008-12-19 20:35 ` jidanni
2008-12-19 20:51 ` Jeff King
2009-01-01 4:24 ` [PATCH] Documentation/git-bundle.txt: Dumping contents of any bundle jidanni
2009-01-01 17:03 ` Johannes Schindelin
2009-01-01 19:21 ` Jeff King
2009-01-01 22:12 ` jidanni [this message]
2009-01-01 23:48 ` Jeff King
2009-01-02 0:10 ` jidanni
2009-01-02 7:15 ` Shawn O. Pearce
2009-01-02 8:27 ` Jeff King
2009-01-02 22:03 ` jidanni
2009-01-01 23:18 ` git ls-tree prints wacko file sizes if it can't find the blob jidanni
2009-01-01 23:47 ` jidanni
2009-01-01 23:52 ` [PATCH] Handle sha1_object_info failures in ls-tree -l Alex Riesen
2009-01-26 19:02 ` [PATCH] git-bundle(1): add no references required simplest case jidanni
2009-01-26 19:53 ` Junio C Hamano
2009-01-29 15:32 ` [PATCH,v2] " jidanni
2009-02-01 23:42 ` jidanni
2009-02-02 0:04 ` Johannes Schindelin
2009-02-02 0:45 ` Junio C Hamano
2009-02-04 0:09 ` jidanni
2009-02-04 2:07 ` Junio C Hamano
2009-02-04 2:18 ` jidanni
2009-02-04 9:15 ` [PATCH] git-bundle doc: update examples Nanako Shiraishi
2009-02-04 15:26 ` Jeff King
2009-02-04 22:44 ` Junio C Hamano
2008-12-19 20:07 ` How to extract files out of a "git bundle", no matter what? 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=87fxk2u13r.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mdl123@verizon.net \
--cc=nico@cam.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.