How can I preserve the dates of the successive versions while importing a project into Git? -
After
I have a folder on my desktop with content:
SABS / | - SABS v0.1b / | -sabs.sh | -Know v0.2b / | -sabs.sh | -Know v0.3b / | -sabs.sh | -Know v0.4b / | -sabs.sh | -Know V0.5b / | -sabs.sh There is a script file inside each of these folders. Each is a different script file associated with them.
I started working on this script before realizing I could use Git.
My question is this: Is it possible to keep history and many times when files were created using Git and amount them? In this way you see then sabsv0.1 this date will appear in which it was created, but not today in which it was imported to Git.
[...] Keep this possible history and time when files use Git Taxes and the amount was made?
By default, resulting in > CD copy Step Where Write a descriptive commit message. If you have multiple versions, you may want to write a shell file for automation of some of thoses steps; You probably want to write a message meaningful every time, though, which can not be automated. Git committed bakes the existing system date bids. However, if you can override this behavior with - Therefore, you could
SABS_git (for example) and flag to do this;
Git init . SABS V0.1b / sabs.sh in SABS_git / . sabs.sh , and commit with the desired date:
Add Git to Git committed sabs.sh --date = & lt; Desired-date & gt; & lt; Desired date & gt; may be, for example, 2014/01/01
Comments
Post a Comment