git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to deal with historic tar-balls

From
Nnn6eumtr <nn6eumtr@gmail.com>
Date
Dec 31, 2011, 19:04 UTC
Message-ID
<4EFF5CDA.5050809@gmail.com>

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: Tomas Carnecky
Message 1 of 12 in “How to deal with historic tar-balls”
  1. nn6eumtrDec 31, 2011
  2. Tomas CarneckyJan 1, 2012
  3. Philip OakleyJan 1, 2012
  4. Philip OakleyJan 1, 2012
  5. Philip OakleyJan 2, 2012
  6. Dirk SüsserottJan 2, 2012
  7. Philip OakleyJan 4, 2012
  8. Dirk SüsserottJan 1, 2012
  9. Neal KreitzingerJan 5, 2012
  10. nn6eumtrJan 7, 2012
  11. Thomas RastJan 7, 2012
  12. Neal KreitzingerJan 7, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.