From: nn6eumtr <nn6eumtr@gmail.com>
To: git@vger.kernel.org
Subject: How to deal with historic tar-balls
Date: Sat, 31 Dec 2011 14:04:58 -0500 [thread overview]
Message-ID: <4EFF5CDA.5050809@gmail.com> (raw)
I have a number of older projects that I want to bring into a git
repository. They predate a lot of the popular scm systems, so they are
primarily a collection of tarballs today.
I'm fairly new to git so I have a couple questions related to this:
- What is the best approach for bringing them in? Do I just create a
repository, then unpack the files, commit them, clean out the directory
unpack the next tarball, and repeat until everything is loaded?
- Do I need to pay special attention to files that are renamed/removed
from version to version?
- If the timestamps change on a file but the actual content does not,
will git treat it as a non-change once it realizes the content hasn't
changed?
- Last, if after loading the repository I find another version of the
files that predates those I've loaded, or are intermediate between two
commits I've already loaded, is there a way to go say that commit B is
actually the ancestor of commit C? (i.e. a->c becomes a->b->c if you
were to visualize the commit timeline or do diffs) Or do I just reload
the tarballs in order to achieve this?
All replies appreciated!
next reply other threads:[~2011-12-31 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 19:04 nn6eumtr [this message]
2012-01-01 0:27 ` How to deal with historic tar-balls Tomas Carnecky
2012-01-01 18:30 ` Philip Oakley
2012-01-01 20:54 ` Philip Oakley
2012-01-02 10:07 ` Philip Oakley
2012-01-02 18:26 ` Dirk Süsserott
2012-01-04 20:04 ` Philip Oakley
2012-01-01 19:04 ` Dirk Süsserott
2012-01-05 15:25 ` Neal Kreitzinger
2012-01-07 1:10 ` nn6eumtr
2012-01-07 1:50 ` Thomas Rast
2012-01-07 19:18 ` Neal Kreitzinger
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=4EFF5CDA.5050809@gmail.com \
--to=nn6eumtr@gmail.com \
--cc=git@vger.kernel.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).