ok, now I'm in this for real, archiving versions of our website project (5k files approx) so here is the workflow: - copy version 1 files into GIT dir - open git bash $ git init $ git add . $ git commit -m "version1" all vanilla ? cool next job = store version 2, so delete version 1 files from GIT dir, copy in version 2 version2 has different files from 1 - which ones? Out of 5k files could be 1% = 50 new ones, and same amount removed. Why should I care, with such a powerful friend as git around, n'est pas? THIS TIME we are going to be CLEVER and use "-a" flag on commit to pick up any files that have been REMOVED (or "deleted" in git-speak) $ git commit -a -m "version2" BUT this does not pick up any new ones that have been added, and when we run $ git status > ../git_status.txt these are referred to as "untracked files" only problem there are 50 ish is there not another flag on git commit to treat any untracked file as a new file ? (would save me typing or creating a list out of these untracked ones and feeding them into git add) I know, I realise now I should have looked up git-commit in the manual - in case its not there, pls enlighten me ! -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
