git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Craig Boston <craig@olyun.gank.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: Efficient way to import snapshots?
Date: Mon, 30 Jul 2007 14:29:23 -0500	[thread overview]
Message-ID: <20070730192922.GB64467@nowhere> (raw)
In-Reply-To: <alpine.LFD.0.999.0707301144180.4161@woody.linux-foundation.org>

On Mon, Jul 30, 2007 at 11:56:56AM -0700, Linus Torvalds wrote:
> It should literally be as easy as doing something like
> 
> 	cd /path/to/cvs/checkout_X
> 	export GIT_DIR=/path/to/git/repo
> 	git add .
> 	git commit -m"Import yyyymmdd snapshot"

Aha!  I didn't know that you could point to a repository with GIT_DIR
and do useful operations without a working directory.  My "master" repo
that gets backed up and cloned everywhere is a bare repo anyway; I had
been cloning it with -s and then using 'git push' to get changes back
into it.

A couple questions on that:

1. Will it notice deleted files?
2. How can I tell it what branch to commit to?

> You'd have to make sure that you have the CVS directories ignored, of 
> course, and if you don't want to change the CVS directory at all (which is 
> a good idea!) you'd need to do that by using the "ignore" file in your 
> GIT_DIR, and just having the CVS entry there, instead of adding a
> ".gitignore" file to the working tree and checking it in.

Not a problem, I'm using cvsup in checkout mode so there are no CVS
dirs.  The checkout directory is an exact snapshot of "What The
Repository Should Look Like."

> The above is totally untested, of course, but I think that's the easiest 
> way to do things like this. In general, it should be *trivial* to do 
> snapshots with git using just about _any_ legacy SCM, exactly because you 
> can keep the whole git setup away from the legacy SCM directories with 
> that "GIT_DIR=.." thing. 

I'll make a backup of my repo and give it a try.

Thanks!

Craig

  reply	other threads:[~2007-07-30 19:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 18:07 Efficient way to import snapshots? Craig Boston
2007-07-30 18:56 ` Linus Torvalds
2007-07-30 19:29   ` Craig Boston [this message]
2007-07-30 19:52     ` Linus Torvalds
2007-07-30 20:10       ` Craig Boston
2007-07-30 21:29         ` Junio C Hamano
2007-07-30 21:49           ` Craig Boston
2007-07-30 21:04       ` Junio C Hamano
2007-07-30 23:19         ` Linus Torvalds
2007-07-30 21:55       ` Junio C Hamano
2007-07-30 23:27         ` Linus Torvalds
2007-07-30 23:59           ` Junio C Hamano
2007-07-31  0:45             ` Linus Torvalds
2007-07-31  0:47               ` Junio C Hamano
2007-07-30 22:20       ` Craig Boston
2007-07-30 23:30         ` Linus Torvalds
2007-07-31  1:17           ` Craig Boston
2007-07-31  1:44             ` Linus Torvalds
2007-07-31  4:23               ` Theodore Tso
2007-07-31 13:53                 ` Craig Boston
2007-07-31 15:50                   ` Linus Torvalds
2007-07-31 16:15                     ` Theodore Tso
2007-07-31  6:23           ` David Kastrup
2007-07-31  7:54             ` Florian Weimer
2007-07-31  8:48               ` David Kastrup
2007-07-30 21:22   ` Jakub Narebski
2007-07-30 21:54 ` David Kastrup

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=20070730192922.GB64467@nowhere \
    --to=craig@olyun.gank.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).