From: Johannes Sixt <J.Sixt@eudaptics•com>
To: git@vger•kernel.org
Cc: Chris Riddoch <riddochc@gmail•com>
Subject: Re: Importing from tarballs; add, rm, update-index?
Date: Fri, 12 Jan 2007 15:39:56 +0100 [thread overview]
Message-ID: <45A79DBC.1795F5C4@eudaptics.com> (raw)
In-Reply-To: 200701121409.l0CE9923015123@laptop13.inf.utfsm.cl
"Horst H. von Brand" wrote:
> Hum... something like the following (completely untested!) should do the
> trick:
>
> cd /basedir
> mkdir codebase; cd codebase; git init-db
> for version in 1.0 1.1 1.1a 1.1b 2.0.0 ...; do
> cd /basedir
> tar xf tarball-$version.tar
> mv codebase-$version/* codebase # Take care to move everything!
> cd codebase
> git add .
> git commit -a -m "Updated to $version"
> rm -rf * # Delete everything except for git stuff
> done
You can let GIT_DIR point somewhere outside the extracted directory.
If the dates of your tarballs are meaningful, you can use something like
this:
export GIT_AUTHOR_DATE="$(date --reference=foo-1.1.tar +%s) -07:00"
-- Hannes
next prev parent reply other threads:[~2007-01-12 14:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 13:41 Importing from tarballs; add, rm, update-index? Chris Riddoch
2007-01-12 14:09 ` Horst H. von Brand
2007-01-12 14:39 ` Johannes Sixt [this message]
2007-01-12 15:39 ` Horst H. von Brand
2007-01-12 14:40 ` Morten Welinder
2007-01-12 18:47 ` Junio C Hamano
2007-01-12 19:11 ` Peter Baumann
2007-01-12 19:43 ` Junio C Hamano
2007-01-12 21:04 ` Peter Baumann
2007-01-13 0:48 ` Junio C Hamano
2007-01-13 9:33 ` Peter Baumann
2007-01-13 11:17 ` Johannes Schindelin
2007-01-13 16:19 ` Peter Baumann
2007-01-13 16:27 ` Julian Phillips
2007-01-13 18:01 ` Junio C Hamano
2007-01-13 16:09 ` Carl Worth
2007-01-13 16:45 ` Brian Gernhardt
2007-01-13 16:48 ` Peter Baumann
2007-01-13 18:54 ` Nicolas Pitre
2007-01-13 19:32 ` Carl Worth
2007-01-13 20:25 ` Junio C Hamano
2007-01-13 20:29 ` Nicolas Pitre
2007-01-13 6:36 ` Brian Gernhardt
2007-01-13 9:36 ` Peter Baumann
2007-01-13 16:31 ` Brian Gernhardt
2007-01-13 18:15 ` Alan Chandler
2007-01-13 19:31 ` Brian Gernhardt
2007-01-13 20:34 ` Shawn O. Pearce
2007-01-14 12:42 ` Johannes Schindelin
2007-01-14 22:42 ` Shawn O. Pearce
2007-01-14 23:49 ` Horst H. von Brand
2007-01-15 1:06 ` Junio C Hamano
2007-01-15 1:12 ` Shawn O. Pearce
2007-01-15 22:46 ` Daniel Barkalow
2007-01-16 0:34 ` Horst H. von Brand
2007-01-16 3:35 ` Daniel Barkalow
2007-01-16 12:12 ` Christian MICHON
2007-01-16 0:51 ` Jakub Narebski
2007-01-13 21:41 ` Horst H. von Brand
2007-01-13 21:47 ` Shawn O. Pearce
2007-01-13 22:04 ` Horst H. von Brand
2007-01-12 19:34 ` Carl Worth
2007-01-12 23:28 ` Johannes Schindelin
2007-01-13 0:01 ` Junio C Hamano
2007-01-12 20:20 ` Jakub Narebski
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=45A79DBC.1795F5C4@eudaptics.com \
--to=j.sixt@eudaptics$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=riddochc@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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