Git svnni tezlashtirishning biron bir usuli bormi?

Men 18 yil davomida, 6000 dan ortiq filial va yarim milliondan ortiq narsalarni olgan SVN omborini Bit Bucket-ga aylantirmoqchiman.

Git svn dastlabki 50k ishlarini taxminan 6 soat ichida o'tkazdi va keyingi 40k konvertatsiyasini 3 kun o'tkazdi. Ikki marta qulab tushdi va ikki marta yo'q bo'ldi, chunki mualliflar yo'qolgan mualliflar tufayli svn jurnallaridan qochib qutulishdi.

Repo kompaniyasining filiallari yanada kengroq foydalanishga kirishgan. Endi u sekinlashdi. Filiallar jiddiy qayg'u keltirmoqda. Har 2-3 daqiqada bitta xatoga yo'l qo'yib bo'lmaydi. Har bir yangi filial butun ishni yanada sekinlashtiradi.

Vaqtni qayerda o'tkazayotganiga ishonchim komil emas. I/u yoki CPU intensivmi? Atlassian SVN joylashgan operatsiyani bajarishni taklif qiladi; mahalliy diskda - tarmoqqa ulanmagan. SVN-dan fayllarni pastga tushirishga vaqt sarflamasdan, bu yordam berishi mumkin emas. Bu filialda ishlayapti va konsolda ko'rsatilmaydi?

Buni Bit Shlangi ichiga olish mumkin deb o'ylamayman. O'ylaymanki, yangi rivojlanishni Bit Bucket-ga ko'chirish va SVN-ni ishga tushirishni davom ettirish yaxshiroq bo'lar edi. Hozirgi almashinuv kursida bir necha yil to'ldirilishi kerak.

3
Bu bir vaqtning o'zida ko'chib, OS Linux
qo'shib qo'ydi muallif eeijlar, manba
Bu bir vaqtning o'zida ko'chib, OS Linux
qo'shib qo'ydi muallif eeijlar, manba
Bu bir martalik ko'chish haqida va siz undan keyingi Gitni ishlatasizmi yoki Git klonidan SVNga qaytib borishni xohlaysizmi?
qo'shib qo'ydi muallif Vampire, manba
Bu bir martalik ko'chish haqida va siz undan keyingi Gitni ishlatasizmi yoki Git klonidan SVNga qaytib borishni xohlaysizmi?
qo'shib qo'ydi muallif Vampire, manba
OS dan qanday ishlashni ishlatasiz? Windows, Linux/Mac-ga nisbatan sekinroq buyurtmalar sifatida ishlatilgan
qo'shib qo'ydi muallif Mykola Gurov, manba
OS dan qanday ishlashni ishlatasiz? Windows, Linux/Mac-ga nisbatan sekinroq buyurtmalar sifatida ishlatilgan
qo'shib qo'ydi muallif Mykola Gurov, manba

6 javoblar

git-svn is not the right tool for one-time conversions of repositories or repository parts. It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not use git-svn, but svn2git which is much more suited for this use-case.

svn2git deb nomlangan ko'p vositalar mavjud, ehtimol bu eng yaxshisi https://github.com/svn-all-fast-export/svn2git . svn2git vositasidan foydalanishni tavsiya etaman. Bu erda men bilganim eng yaxshi va qoidalar fayllari bilan nima qila olishingiz juda moslashuvchan.

Siz istagan natija ishlab chiqarish uchun svn2git s qoidalar faylini osonlikcha tuzata olasiz va u tezroq gazlonlardir.

Agar repository tarixingiz haqida 100% bo'lmasangiz http-dan svneverever : //blog.hartwork.org/? p = 763 Gitni ko'chirishda SVN ombori tarixini o'rganish uchun ajoyib vosita.


git-svn ni ishga tushirish osonroq bo'lsa-da, git-svn o'rniga KDE svn2git dan foydalanishning yana bir sababi yuqoriroq, uning moslashuvchanligi bilan bir qatorda:

  • the history is rebuilt much better and cleaner by svn2git (if the correct one is used), this is especially the case for more complex histories with branches and merges and so on
  • the tags are real tags and not branches in Git
  • with git-svn the tags contain an extra empty commit which also makes them not part of the branches, so a normal fetch will not get them until you give --tags to the command as by default only tags pointing to fetched branches are fetched also. With the proper svn2git tags are where they belong
  • if you changed layout in SVN you can easily configure this with svn2git, with git-svn you will loose history eventually
  • with svn2git you can also split one SVN repository into multiple Git repositories easily
  • or combine multiple SVN repositories in the same SVN root into one Git repository easily
  • the conversion is a gazillion times faster with the correct svn2git than with git-svn

Ko'rib turganingizdek, git-svn ning yomonligi va KDE svn2git ning ustunligi juda ko'p. :-)

2
qo'shib qo'ydi

git-svn is not the right tool for one-time conversions of repositories or repository parts. It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not use git-svn, but svn2git which is much more suited for this use-case.

svn2git deb nomlangan ko'p vositalar mavjud, ehtimol bu eng yaxshisi https://github.com/svn-all-fast-export/svn2git . svn2git vositasidan foydalanishni tavsiya etaman. Bu erda men bilganim eng yaxshi va qoidalar fayllari bilan nima qila olishingiz juda moslashuvchan.

Siz istagan natija ishlab chiqarish uchun svn2git s qoidalar faylini osonlikcha tuzata olasiz va u tezroq gazlonlardir.

Agar repository tarixingiz haqida 100% bo'lmasangiz http-dan svneverever : //blog.hartwork.org/? p = 763 Gitni ko'chirishda SVN ombori tarixini o'rganish uchun ajoyib vosita.


git-svn ni ishga tushirish osonroq bo'lsa-da, git-svn o'rniga KDE svn2git dan foydalanishning yana bir sababi yuqoriroq, uning moslashuvchanligi bilan bir qatorda:

  • the history is rebuilt much better and cleaner by svn2git (if the correct one is used), this is especially the case for more complex histories with branches and merges and so on
  • the tags are real tags and not branches in Git
  • with git-svn the tags contain an extra empty commit which also makes them not part of the branches, so a normal fetch will not get them until you give --tags to the command as by default only tags pointing to fetched branches are fetched also. With the proper svn2git tags are where they belong
  • if you changed layout in SVN you can easily configure this with svn2git, with git-svn you will loose history eventually
  • with svn2git you can also split one SVN repository into multiple Git repositories easily
  • or combine multiple SVN repositories in the same SVN root into one Git repository easily
  • the conversion is a gazillion times faster with the correct svn2git than with git-svn

Ko'rib turganingizdek, git-svn ning yomonligi va KDE svn2git ning ustunligi juda ko'p. :-)

2
qo'shib qo'ydi

git-svn is not the right tool for one-time conversions of repositories or repository parts. It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not use git-svn, but svn2git which is much more suited for this use-case.

svn2git deb nomlangan ko'p vositalar mavjud, ehtimol bu eng yaxshisi https://github.com/svn-all-fast-export/svn2git . svn2git vositasidan foydalanishni tavsiya etaman. Bu erda men bilganim eng yaxshi va qoidalar fayllari bilan nima qila olishingiz juda moslashuvchan.

Siz istagan natija ishlab chiqarish uchun svn2git s qoidalar faylini osonlikcha tuzata olasiz va u tezroq gazlonlardir.

Agar repository tarixingiz haqida 100% bo'lmasangiz http-dan svneverever : //blog.hartwork.org/? p = 763 Gitni ko'chirishda SVN ombori tarixini o'rganish uchun ajoyib vosita.


git-svn ni ishga tushirish osonroq bo'lsa-da, git-svn o'rniga KDE svn2git dan foydalanishning yana bir sababi yuqoriroq, uning moslashuvchanligi bilan bir qatorda:

  • the history is rebuilt much better and cleaner by svn2git (if the correct one is used), this is especially the case for more complex histories with branches and merges and so on
  • the tags are real tags and not branches in Git
  • with git-svn the tags contain an extra empty commit which also makes them not part of the branches, so a normal fetch will not get them until you give --tags to the command as by default only tags pointing to fetched branches are fetched also. With the proper svn2git tags are where they belong
  • if you changed layout in SVN you can easily configure this with svn2git, with git-svn you will loose history eventually
  • with svn2git you can also split one SVN repository into multiple Git repositories easily
  • or combine multiple SVN repositories in the same SVN root into one Git repository easily
  • the conversion is a gazillion times faster with the correct svn2git than with git-svn

Ko'rib turganingizdek, git-svn ning yomonligi va KDE svn2git ning ustunligi juda ko'p. :-)

2
qo'shib qo'ydi

Siz SVN-ning tarixini ko'chirmasdan faqatgina bitta filni joriy havzaning tarkibidan yuborishingiz mumkin.

0
qo'shib qo'ydi

Siz SVN-ning tarixini ko'chirmasdan faqatgina bitta filni joriy havzaning tarkibidan yuborishingiz mumkin.

0
qo'shib qo'ydi

Siz SVN-ning tarixini ko'chirmasdan faqatgina bitta filni joriy havzaning tarkibidan yuborishingiz mumkin.

0
qo'shib qo'ydi