From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Mark Levedahl <mdl123@verizon.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add git-bundle - pack objects and references for disconnected transfer
Date: Fri, 16 Feb 2007 12:57:20 +0100 [thread overview]
Message-ID: <45D59C20.6050708@fs.ei.tum.de> (raw)
In-Reply-To: <20070216065421.GG28894@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Shawn O. Pearce wrote:
> Mark Levedahl <mdl123@verizon.net> wrote:
>> +# create the tar file, clean up
>> +tar cf "$bfile" --absolute-names --transform="s,$tmp-,," \
>> + --verbose --show-transformed-names \
>> + "$references" "$pack"
>
> I'm not sure this will work on FreeBSD. Both 5.1 and 6.1 use tar
> that does not know about --absolute-names, --transform, --verbose,
> or --show-transformed-names.
for portability, pax is the official choice :) and it can even do path name modifications with -s. but why again are we using tar there? this data could easiliy be put in one mixed text/binary file, starting out with
#!/bin/sh
echo "This is a git bundle. Use git-unbundle to process me." >&1
exit
### DATA ###
or so
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-02-16 11:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 0:19 Respun - Scripts to use bundles to move data between repos Mark Levedahl
2007-02-16 0:19 ` [PATCH] Add git-bundle - pack objects and references for disconnected transfer Mark Levedahl
2007-02-16 0:19 ` [PATCH] Add git-unbundle - unpack " Mark Levedahl
2007-02-16 0:19 ` [PATCH] Include git-bundle and git-unbundle in Makefile Mark Levedahl
2007-02-16 0:19 ` [PATCH] Create documentation for git-bundle Mark Levedahl
2007-02-16 0:19 ` [PATCH] Create documentation for git-unbundle Mark Levedahl
2007-02-16 0:19 ` [PATCH] Link git-bundle and git-unbundle docs from git(7) Mark Levedahl
2007-02-16 2:24 ` [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Junio C Hamano
2007-02-16 2:40 ` Linus Torvalds
2007-02-16 6:38 ` Mark Levedahl
2007-02-16 6:48 ` Shawn O. Pearce
2007-02-16 7:31 ` Junio C Hamano
2007-02-16 7:45 ` Shawn O. Pearce
2007-02-16 6:22 ` Mark Levedahl
2007-02-16 7:24 ` Junio C Hamano
2007-02-16 2:11 ` [PATCH] Add git-bundle - pack " Junio C Hamano
2007-02-16 4:41 ` Shawn O. Pearce
2007-02-16 7:28 ` Junio C Hamano
2007-02-16 6:39 ` Mark Levedahl
2007-02-16 6:54 ` Shawn O. Pearce
2007-02-16 11:57 ` Simon 'corecode' Schubert [this message]
2007-02-16 4:37 ` Respun - Scripts to use bundles to move data between repos Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 12:45 Re: [PATCH] Add git-bundle - pack objects and references for disconnected transfer Mark Levedahl
2007-02-16 13:25 ` Simon 'corecode' Schubert
2007-02-16 13:44 ` Johannes Schindelin
2007-02-16 23:25 ` Mark Levedahl
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=45D59C20.6050708@fs.ei.tum.de \
--to=corecode@fs.ei.tum.de \
--cc=git@vger.kernel.org \
--cc=mdl123@verizon.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 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).