Hi Steve, You may need to elaborate a bit more as the options may be wider than you imply, and so needs more information to make the choice.
I'm going to guess that what you had was a series of project snapshots (on one of my projects we would 'compressed zip' the super-top level folder, and then update the folder name with its new/next version suffix). Thus we had a whole load of these snapshots, and I created short script that would extract each zip to a working directory, and then commit that directory with the date set to the zip date, then clean the directory and do the next zip. This created a simplistic git project structure that captured all the release points. It was a small team of 2-3 people hence the original method was pretty effective locally, and a adding the zips to the git repo gives a good view of the history. If your archive is arranged on some other basis, then a bit more info... Philip On Tuesday, February 18, 2020 at 1:27:53 PM UTC, Steve Cobrin wrote: > > Historically we were really old-school and stored different versions of > files with a timestamp appended to the end of the filename, and stashed > them into a directory, e.g. > > foo > .archive/YYYYmmdd > > Now we want to put all the instances of the file int a Git repo, is there > any easy way to do it? > > Cheers > Steve > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/cbb36006-6839-4c3c-a10b-3278b132322b%40googlegroups.com.
