[git-users] Re: How to move manually-versionned files to git (version control)?
Thank you ! I suppose that there is no formal way to import all of these in git. Is n't it? I expected that there would be such documented procedure or command(!) in git (or other version control systems) to help newcomers to import their old changes (commits)... Best regards, Konstantinos On Monday, November 24, 2014 2:55:12 PM UTC+2, Konstantinos Mavroudakis wrote: I am preparing to move the source code for a project to git. There was no other version control in the past. I maintained old versions of file: myfile with change dates at the end as follows: myfile-d20130629, myfile-d20140223 myfile-d20141019 etc. myfile is the latest version. Is there a way (using git or other means) to integrate these old files to git under myfile name versioning preserving the individual old commits e.g (commit d20130629, commit d20140223 commit d20141019)? Moreover, is it possible to add the correct (past) date in each one of these commits? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Re: How to move manually-versionned files to git (version control)?
On Wed, Nov 26, 2014 at 8:35 AM, Konstantinos Mavroudakis kmavrouda...@gmail.com wrote: Thank you ! I suppose that there is no formal way to import all of these in git. Is n't it? I expected that there would be such documented procedure or command(!) in git (or other version control systems) to help newcomers to import their old changes (commits)... From what other source control? git has a fast-import command in the basic command set. But it isn't normally used by an individual. I should warn you that I am not anywhere close to being a git expert. Hopefully one of the wise old ones will come along side with some really helpful advice Best regards, Konstantinos -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Re: How to move manually-versionned files to git (version control)?
From zero source control :) i.e. no source control On Wednesday, November 26, 2014 4:48:02 PM UTC+2, John McKown wrote: On Wed, Nov 26, 2014 at 8:35 AM, Konstantinos Mavroudakis kmavro...@gmail.com javascript: wrote: Thank you ! I suppose that there is no formal way to import all of these in git. Is n't it? I expected that there would be such documented procedure or command(!) in git (or other version control systems) to help newcomers to import their old changes (commits)... From what other source control? git has a fast-import command in the basic command set. But it isn't normally used by an individual. I should warn you that I am not anywhere close to being a git expert. Hopefully one of the wise old ones will come along side with some really helpful advice Best regards, Konstantinos -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Re: How to move manually-versionned files to git (version control)?
On Wed, Nov 26, 2014 at 8:52 AM, Konstantinos Mavroudakis kmavrouda...@gmail.com wrote: From zero source control :) i.e. no source control My bad. When you said import their comments, I just ASSuMEd that those comments already existed in another source control system. Going back to your original post where you basically encoded the date into the file name as a type of commit point, I guess that the git people didn't look at some sort of import simply because there is no real standard about such. I guess that they felt that anyone who was using a personal ad hoc system that they designed themselves would just need to convert to git as best as they could. On Wednesday, November 26, 2014 4:48:02 PM UTC+2, John McKown wrote: On Wed, Nov 26, 2014 at 8:35 AM, Konstantinos Mavroudakis kmavro...@gmail.com wrote: Thank you ! I suppose that there is no formal way to import all of these in git. Is n't it? I expected that there would be such documented procedure or command(!) in git (or other version control systems) to help newcomers to import their old changes (commits)... From what other source control? git has a fast-import command in the basic command set. But it isn't normally used by an individual. I should warn you that I am not anywhere close to being a git expert. Hopefully one of the wise old ones will come along side with some really helpful advice Best regards, Konstantinos -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- 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. For more options, visit https://groups.google.com/d/optout. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- 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. For more options, visit https://groups.google.com/d/optout.
