Hi, >> The problem is that git (or mercurial, another distributed scm) don't >> record empty >> directories in the history. So, when you clone a git repository, the >> directory isn't >> created. > Sounds like a rather questionable design decision for me. Are there any > advantages of this approach? As far as I know the argumentation goes along these lines: If a program requires a directory to write i.e. its log files into it's probably a good idea to have the program create that directory if not already present. In the same way if a build script requires a directory to write an object / a binray into it's probably a good idea to have the script create that directory. GIT et al don't see themselves as helpers to programs or build scripts but as content management systems. Please note that this isn't my personal opinion. Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Aug 22 09:58:08 2012
This archive was generated by hypermail 2.1.8 : 2012-08-22 09:58:12 CEST