{"thread":{"id":"3078","subject":"cvs-migration.txt","startedAt":"2006-01-15T19:58:04Z","lastAt":"2006-01-16T01:31:49Z","messageCount":3,"participants":["J. Bruce Fields","Junio C Hamano","Martin Langhoff"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14690","messageId":"20060115195804.GD3985@fieldses.org","threadId":"3078","inReplyTo":null,"subject":"cvs-migration.txt","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2006-01-15T19:58:04Z","receivedAt":"2006-01-15T19:58:04Z","isPatch":false,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"I find the following sentence from cvs-migration.txt slightly confusing:\n\n\t\"The cut-off is date-based, so don't change the branches that\n\twere imported from CVS.\"\n\nI assume the branches referrred to are the target git branches, not the\nsource CVS branches?  (And are date-based cut-offs really the essential\nreason for this restriction?)\n\n--b.\n"},{"id":"14697","messageId":"7vy81h2o3a.fsf@assigned-by-dhcp.cox.net","threadId":"3078","inReplyTo":"20060115195804.GD3985@fieldses.org","subject":"Re: cvs-migration.txt","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-15T21:11:37Z","receivedAt":"2006-01-15T21:11:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"J. Bruce Fields\" <bfields@fieldses.org> writes:\n\n> I find the following sentence from cvs-migration.txt slightly confusing:\n>\n> \t\"The cut-off is date-based, so don't change the branches that\n> \twere imported from CVS.\"\n>\n> I assume the branches referrred to are the target git branches, not the\n> source CVS branches?  (And are date-based cut-offs really the essential\n> reason for this restriction?)\n\nSorry, I cannot answer this one immediately without researching\nmyself; I do not use cvsimport.\n\nThe way I read the code agrees with you.  The date from the\ntopmost commit from each git branch is read, and used to limit\nthe changes we read from CVS into them.  The code reads from\n\"author date\", which is technically incorrect, but what we are\nsaying here is that you should never commit into these branches\nyourself and let cvsimport be the only one that touch them, so\nusing commiter date and author date would not make a difference.\n"},{"id":"14704","messageId":"46a038f90601151731vc72835dja390b7934a6b575f@mail.gmail.com","threadId":"3078","inReplyTo":"7vy81h2o3a.fsf@assigned-by-dhcp.cox.net","subject":"Re: cvs-migration.txt","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2006-01-16T01:31:49Z","receivedAt":"2006-01-16T01:31:49Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 1/16/06, Junio C Hamano <junkio@cox.net> wrote:\n> what we are\n> saying here is that you should never commit into these branches\n> yourself and let cvsimport be the only one that touch them, so\n> using commiter date and author date would not make a difference.\n\nExactly. You should make a new head off the one imported from cvs, and\nwork there. This supports continued use of cvsimport if the cvs repo\nis still active. To bring in those changes you will have to merge them\ninto your branch.\n\nIf you are 200% certain that the cvs repo is going to be removed\nimmediately, you can ignore this advice. Run the cvsimport once, and\nthen start developing on top. If you do this, however, don't run that\ncvsimport ever again, for it will mess up things royally ;)\n\nBut it's a bad idea to keep using the same branches in any case. Life\nis saner if you work on new heads.\n\n\nmartin\n"}]}