{"thread":{"id":"23915","subject":"Migrate from svn to git","startedAt":"2010-05-26T15:13:51Z","lastAt":"2010-06-01T14:23:21Z","messageCount":9,"participants":["Matthias Fechner","Ævar Arnfjörð Bjarmason","hasen j","Nazri Ramliy","Michael Witten"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"142377","messageId":"4BFD3AAF.4080403@fechner.net","threadId":"23915","inReplyTo":null,"subject":"Migrate from svn to git","fromName":"Matthias Fechner","fromEmail":"idefix@fechner.net","sentAt":"2010-05-26T15:13:51Z","receivedAt":"2010-05-26T15:13:51Z","isPatch":false,"sender":{"key":"idefix@fechner.net","avatar":"https://gravatar.com/avatar/3bbc5542677a77cb9b75262e4ad2eeb04a0960f0b8dec89a178db17cf472cce7?d=mp&s=160"},"body":"Hi,\n\nI hope that is the correct list to ask some questions.\nI understood that the idea behind git is completely different and I like \nthe idea behind git.\n\nBut for the svn repository I want to convert I need some features and \nI'm not sure how / if to implement them in git.\n\nCorrently the svn repo is divided into trunk branches and tags.\nIn each of this directory like trunk i have directories like hardware, \nsoftware, docu and more.\n\nFor each of this subdirectories I have usergroups defined which has no \naccess, read access or rw access.\n\nIf I understood the manual correctly I can stick on that structure and \neasily work here with the unix-permission to grant access to the folders?\nI think I have to test then acl with freebsd to have more then one group \nfor each directory.\n\n\nThe second question is, I someone commits some files with svn an email \nis sent to a svn-commit mailinglist so changes can easily be discussed.\nThe current mail is sent in html format with a colored diff, so it is \neasier to read.\n\nIs something similar possible with git or do you suggest a complete \napproach?\n\nThanks a lot for answers.\n\nBye,\nMatthias\n\n-- \n\"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning.\" -- Rich Cook\n"},{"id":"142380","messageId":"AANLkTikD6Op5TO0EtQWLQ0N6zD0Kr-pltW76rY1Dvx5D@mail.gmail.com","threadId":"23915","inReplyTo":"4BFD3AAF.4080403@fechner.net","subject":"Re: Migrate from svn to git","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-05-26T16:23:35Z","receivedAt":"2010-05-26T16:23:35Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Wed, May 26, 2010 at 15:13, Matthias Fechner <idefix@fechner.net> wrote:\n> I hope that is the correct list to ask some questions.\n> I understood that the idea behind git is completely different and I like the\n> idea behind git.\n>\n> But for the svn repository I want to convert I need some features and I'm\n> not sure how / if to implement them in git.\n>\n> Corrently the svn repo is divided into trunk branches and tags.\n> In each of this directory like trunk i have directories like hardware,\n> software, docu and more.\n>\n> For each of this subdirectories I have usergroups defined which has no\n> access, read access or rw access.\n>\n> If I understood the manual correctly I can stick on that structure and\n> easily work here with the unix-permission to grant access to the folders?\n> I think I have to test then acl with freebsd to have more then one group for\n> each directory.\n\nNo. Git isn't centralized. Anyone can clone the repo and change\nanything the want. You implement control by setting a policy on what\nyou merge back into your tree, which is considered canonical.\n\nThere are several on-commit filtering programs available that can do\nthat automatically based on paths within the repository.\n\n> The second question is, I someone commits some files with svn an email is\n> sent to a svn-commit mailinglist so changes can easily be discussed.\n> The current mail is sent in html format with a colored diff, so it is easier\n> to read.\n>\n> Is something similar possible with git or do you suggest a complete\n> approach?\n\nThere are a lot of these scripts available in contrib and elsewhere.\n"},{"id":"142381","messageId":"AANLkTinTYWQflbvlWVjDKD3gtOyQxDrSZ7QKhy4eI77_@mail.gmail.com","threadId":"23915","inReplyTo":"4BFD3AAF.4080403@fechner.net","subject":"Re: Migrate from svn to git","fromName":"hasen j","fromEmail":"hasan.aljudy@gmail.com","sentAt":"2010-05-26T16:26:04Z","receivedAt":"2010-05-26T16:26:04Z","isPatch":false,"sender":{"key":"hasan.aljudy@gmail.com","avatar":"https://gravatar.com/avatar/47314b4bfcc6ba6685a811d9697fe60e90602acec0e24b9bf48bd0a97307f7c2?d=mp&s=160"},"body":"> Corrently the svn repo is divided into trunk branches and tags.\n> In each of this directory like trunk i have directories like hardware,\n> software, docu and more.\n>\n> For each of this subdirectories I have usergroups defined which has no\n> access, read access or rw access.\n>\n> If I understood the manual correctly I can stick on that structure and\n> easily work here with the unix-permission to grant access to the folders?\n> I think I have to test then acl with freebsd to have more then one group for\n> each directory.\n\nAs far as I know, git doesn't track permissions (except for the execute bit).\n\n>\n>\n> The second question is, I someone commits some files with svn an email is\n> sent to a svn-commit mailinglist so changes can easily be discussed.\n> The current mail is sent in html format with a colored diff, so it is easier\n> to read.\n>\n> Is something similar possible with git or do you suggest a complete\n> approach?\n\nI've seen it done, e.g. xfce4-commits mailing list.\nhttp://foo-projects.org/pipermail/xfce4-commits/\n"},{"id":"142383","messageId":"AANLkTilNlttIQxyhMJz8_wiOQX5OaL0UahsE54mv6rQ3@mail.gmail.com","threadId":"23915","inReplyTo":"4BFD3AAF.4080403@fechner.net","subject":"Re: Migrate from svn to git","fromName":"Nazri Ramliy","fromEmail":"ayiehere@gmail.com","sentAt":"2010-05-26T17:04:11Z","receivedAt":"2010-05-26T17:04:11Z","isPatch":false,"sender":{"key":"ayiehere@gmail.com","avatar":"https://avatars.githubusercontent.com/u/164756?v=4"},"body":"On Wed, May 26, 2010 at 11:13 PM, Matthias Fechner <idefix@fechner.net> wrote:\n> For each of this subdirectories I have usergroups defined which has no\n> access, read access or rw access.\n>\n> If I understood the manual correctly I can stick on that structure and\n> easily work here with the unix-permission to grant access to the folders?\n> I think I have to test then acl with freebsd to have more then one group for\n> each directory.\n\nDealing with acl sounds like a lot of work and complications to me.\nHave a look at gitolite. It is covered quite nice in the progit book [1]\n\n> The second question is, I someone commits some files with svn an email is\n> sent to a svn-commit mailinglist so changes can easily be discussed.\n> The current mail is sent in html format with a colored diff, so it is easier\n> to read.\n>\n> Is something similar possible with git or do you suggest a complete\n> approach?\n\nFor this you might want to look at Gerrit [2]. It's a web-based code\nreview. Although it is not email based (AFAIK).\n\nnazri.\n\n\n[1] http://progit.org/book/ch4-8.html\n[2] http://code.google.com/p/gerrit/\n"},{"id":"142399","messageId":"4BFE0F0A.301@fechner.net","threadId":"23915","inReplyTo":"AANLkTilNlttIQxyhMJz8_wiOQX5OaL0UahsE54mv6rQ3@mail.gmail.com","subject":"Re: Migrate from svn to git","fromName":"Matthias Fechner","fromEmail":"idefix@fechner.net","sentAt":"2010-05-27T06:19:54Z","receivedAt":"2010-05-27T06:19:54Z","isPatch":false,"sender":{"key":"idefix@fechner.net","avatar":"https://gravatar.com/avatar/3bbc5542677a77cb9b75262e4ad2eeb04a0960f0b8dec89a178db17cf472cce7?d=mp&s=160"},"body":"Am 26.05.10 19:04, schrieb Nazri Ramliy:\n>\n> Dealing with acl sounds like a lot of work and complications to me.\n> Have a look at gitolite. It is covered quite nice in the progit book [1]\n>    \n\nthanks for the link i will read the documentation to get more \ninformation about it, but the first look is very promising.\n\nMatthias\n\n-- \n\"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning.\" -- Rich Cook\n"},{"id":"142400","messageId":"4BFE0F93.4050600@fechner.net","threadId":"23915","inReplyTo":"AANLkTikD6Op5TO0EtQWLQ0N6zD0Kr-pltW76rY1Dvx5D@mail.gmail.com","subject":"Re: Migrate from svn to git","fromName":"Matthias Fechner","fromEmail":"idefix@fechner.net","sentAt":"2010-05-27T06:22:11Z","receivedAt":"2010-05-27T06:22:11Z","isPatch":false,"sender":{"key":"idefix@fechner.net","avatar":"https://gravatar.com/avatar/3bbc5542677a77cb9b75262e4ad2eeb04a0960f0b8dec89a178db17cf472cce7?d=mp&s=160"},"body":"Am 26.05.10 18:23, schrieb Ævar Arnfjörð Bjarmason:\n>\n> There are a lot of these scripts available in contrib and elsewhere.\n>    \n\nthanks, i will start then in the contrib folder.\nIs it possible in git to attach script like hooks in svn if someone pull \ncontent to the repo?\n\nMatthias\n\n-- \n\"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning.\" -- Rich Cook\n"},{"id":"142606","messageId":"AANLkTinKsGPo0-ETmVOSH6fY64GLLwVm2dNBGyjAvrin@mail.gmail.com","threadId":"23915","inReplyTo":"4BFD3AAF.4080403@fechner.net","subject":"Re: Migrate from svn to git","fromName":"Michael Witten","fromEmail":"mfwitten@gmail.com","sentAt":"2010-05-31T12:01:44Z","receivedAt":"2010-05-31T12:01:44Z","isPatch":false,"sender":{"key":"mfwitten@gmail.com","avatar":"https://avatars.githubusercontent.com/u/597101?v=4"},"body":"On Wed, May 26, 2010 at 10:13, Matthias Fechner <idefix@fechner.net> wrote:\n> The second question is, I someone commits\n> some files with svn an email is sent to a\n> svn-commit mailinglist so changes can easily\n> be discussed.\n\nShouldn't the discussion happen before the commit?\n\n> The current mail is sent in html format with\n> a colored diff, so it is easier to read.\n\nI would rather receive the raw diff and let my own preferred tools\ndisplay the information in way that I personally like.\n\nKeep in mind that `git diff' is capable of displaying the diff with color.\n\nMichael Witten\n"},{"id":"142653","messageId":"4C04ADFC.9020309@fechner.net","threadId":"23915","inReplyTo":"AANLkTinKsGPo0-ETmVOSH6fY64GLLwVm2dNBGyjAvrin@mail.gmail.com","subject":"Re: Migrate from svn to git","fromName":"Matthias Fechner","fromEmail":"idefix@fechner.net","sentAt":"2010-06-01T06:51:40Z","receivedAt":"2010-06-01T06:51:40Z","isPatch":false,"sender":{"key":"idefix@fechner.net","avatar":"https://gravatar.com/avatar/3bbc5542677a77cb9b75262e4ad2eeb04a0960f0b8dec89a178db17cf472cce7?d=mp&s=160"},"body":"Hi Michael,\n\nAm 31.05.10 14:01, schrieb Michael Witten:\n> Shouldn't the discussion happen before the commit?\n>    \n\nin most of the cases it is not necessary, but the diff mails are used as \nan additional review step and sometimes additional changes follow.\nBut it is a way to do it and people are used to do it.\n\nI'm thinking more and more about it and I think the best solution is to \nkeep svn as the central repo and do a git svn clone from there, so I \nhave the advantage of the existing infrastructure and will get the nice \nfeatures from git.\n\nMatthias\n\n-- \n\"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning.\" -- Rich Cook\n"},{"id":"142684","messageId":"AANLkTimRzqeffooPPHEVE9_ccZojmZG-SudKTx_6M7ho@mail.gmail.com","threadId":"23915","inReplyTo":"4C04ADFC.9020309@fechner.net","subject":"Re: Migrate from svn to git","fromName":"Michael Witten","fromEmail":"mfwitten@gmail.com","sentAt":"2010-06-01T14:23:21Z","receivedAt":"2010-06-01T14:23:21Z","isPatch":false,"sender":{"key":"mfwitten@gmail.com","avatar":"https://avatars.githubusercontent.com/u/597101?v=4"},"body":"On Tue, Jun 1, 2010 at 01:51, Matthias Fechner <idefix@fechner.net> wrote:\n> I'm thinking more and more about it and I think the best solution is to keep\n> svn as the central repo and do a git svn clone from there, so I have the\n> advantage of the existing infrastructure and will get the nice features from\n> git.\n\nThat's probably a good way to get people started with git.\n\nHowever, git hooks SEEM like they should be enough for your purposes.\n\nFor permissions, see contrib/hooks/update-paranoid:\n\n  http://git.kernel.org/?p=git/git.git;h=d18b317b2f018d1d1a5a9677a7bdaf8956d65186\n\nand for emails, see see contrib/hooks/post-receive-email:\n\n  http://git.kernel.org/?p=git/git.git;h=30ae63d74da065a31cced0b161708680f39c04c0\n\n(Sorry if gmail mangles those urls).\n\nSincerely,\nMichael Witten\n"}]}