Closed Bug 455727 Opened 12 years ago Closed 12 years ago
import calendar/ into comm-central
calendar/ source is currently pulled into comm-central working directories from cvs trunk, this bug is about importing it directly into comm-central before fixing the build system to build Sunbird from there in bug 453330. At today's calendar status meeting, it was decided to use tomorrow's CVS HEAD as a base for that import - I'll perform it according to that.
Don't forget importing mozilla/other-license/branding/sunbird please.
This is the client.py patch to remove pulling of calendar once we import it directly into comm-central. ssitter: Thanks for the reminder!
Attachment #339107 - Flags: review?(bugspam.Callek)
Comment on attachment 339107 [details] [diff] [review] remove pulling of calendar from client.py This looks good, but I am going to test if we actually should introduce a form of garbage collection into here for these CVS pieces that move to Hg. To potentially prevent local bustages.
Comment on attachment 339107 [details] [diff] [review] remove pulling of calendar from client.py actually per IRC chatter: we can't force client.py to actually remove these files and at the same time be sure the client computer doesn't inherit them from comm-central first. So even if keeping it there could break clients (temporarily) we'll be stuck either way... so bite the bullet and don't block on meaningless code complexity.
Attachment #339107 - Flags: review?(bugspam.Callek) → review+
client.py patch pushed as http://hg.mozilla.org/comm-central/rev/d4b728dc9da4 and: http://hg.mozilla.org/comm-central/rev/7c0bfdcda673 initial import of code from CVS tag HG_COMM_INITIAL_IMPORT at 2008-09-18 07:11:38 PST, imported and tagged cvs.mozilla.org modules: mozilla/calendar mozilla/other-licenses/branding/sunbird/
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Was it intentional to also push all the .cvsignore files?
D'oh, now I see that you already noticed it. Ignore me!
You need to log in before you can comment on or make changes to this bug.