Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
ti, 2010-06-15 kello 13:18 +0900, David kirjoitti: On 06/15/2010 12:15 PM, Vincent Davis wrote: Is this http://github.com/cournape/numpy going to become the git repo? No, this is just a mirror of the svn repo, and used by various developers to do their own stuff. That's a mirror of a mirror, the master SVN mirror is here: http://projects.scipy.org/git/numpy/ -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Is this http://github.com/cournape/numpy going to become the git repo? I guess I am wondering what the progress is of the transition? Vincent On Sun, Jun 6, 2010 at 7:43 PM, David da...@silveregg.co.jp wrote: On 06/05/2010 11:43 PM, Pauli Virtanen wrote: Fri, 04 Jun 2010 15:28:52 -0700, Matthew Brett wrote: I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? Just to be clear, this has nothing to do with accounts on github, or any registered thing. This is *only* about username/email as recognized by git itself (as recorded in the commit objects). Actually - isn't it better if people do give you their github username / email combo - assuming that's the easiest combo to work with later? I think the Github user name is not really needed here, as what goes into the history is the Git ID: name + email address. Indeed. IOW, the output of git config user.name git config user.email if you already use git is all that I need, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On 06/15/2010 12:15 PM, Vincent Davis wrote: Is this http://github.com/cournape/numpy going to become the git repo? No, this is just a mirror of the svn repo, and used by various developers to do their own stuff. I guess I am wondering what the progress is of the transition? It is progressing, and we will keep people posted when there is something to show, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On 06/05/2010 11:43 PM, Pauli Virtanen wrote: Fri, 04 Jun 2010 15:28:52 -0700, Matthew Brett wrote: I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? Just to be clear, this has nothing to do with accounts on github, or any registered thing. This is *only* about username/email as recognized by git itself (as recorded in the commit objects). Actually - isn't it better if people do give you their github username / email combo - assuming that's the easiest combo to work with later? I think the Github user name is not really needed here, as what goes into the history is the Git ID: name + email address. Indeed. IOW, the output of git config user.name git config user.email if you already use git is all that I need, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Fri, 04 Jun 2010 15:28:52 -0700, Matthew Brett wrote: I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? Just to be clear, this has nothing to do with accounts on github, or any registered thing. This is *only* about username/email as recognized by git itself (as recorded in the commit objects). Actually - isn't it better if people do give you their github username / email combo - assuming that's the easiest combo to work with later? I think the Github user name is not really needed here, as what goes into the history is the Git ID: name + email address. -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Fri, 04 Jun 2010 15:19:27 -0700, Dan Roberts wrote: Sorry to interrupt, but do you have a usable, up to date cloneable git repository somewhere? I noticed that you had a repository on github, but it's about a month out of date. I understand if what you're working on isn't ready to be cloned from yet. In the meantime I can use git-svn, but I figured if you had something better, I'd use that. See also http://projects.scipy.org/numpy/wiki/GitMirror ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Hi, Actually - isn't it better if people do give you their github username / email combo - assuming that's the easiest combo to work with later? I think the Github user name is not really needed here, as what goes into the history is the Git ID: name + email address. Yes, sorry, of course you're right, the 'name' is nothing to do with the github username. I guess we do need to send the Git ID we like to use though (in my case Matthew Brett matthew.br...@gmail.com). See you, Matthew ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Sorry to interrupt, but do you have a usable, up to date cloneable git repository somewhere? I noticed that you had a repository on github, but it's about a month out of date. I understand if what you're working on isn't ready to be cloned from yet. In the meantime I can use git-svn, but I figured if you had something better, I'd use that. Thanks, Dan On Jun 1, 2010 12:59 AM, David Cournapeau courn...@gmail.com wrote: Hi there, I have looked back into the way to convert the existing numpy svn repository into git. It went quite smoothly using svn2git (developed by the KDE team for their own transition), but there are a few questions which need to be answered: - Shall we keep the old svn branches ? I think most of them are just cruft, and can be safely removed We would then just keep the release branches (in maintenance/***) - Tag conversion: svn has no notion of tags, so translating them into git tags cannot be done automatically in a safely manner (and we do have some rewritten tags in the svn repo). I was thinking about creating a small script to create them manually afterwards for the releases, in the svntags/***. - Author conversion: according to git, there are around 50 committers in numpy. Several of them are double and should be be merged I think (kern vs rkern, Travis' accounts as well), but there is also the option to set up real emails. Since email are private, I don't want to just scrape them without asking permission first. I don't know how we should proceed here. The author conversion needs to be decided upfront (as changing name in committers will cause to change every sha256), tags and scrapping branches may be done later. Last time we discussed things, there were some concerns about space: the numpy git repo is around 17 Mb for the full history, 36 Mb if one includes the working tree, compared to 43 Mb for a trunk checkout from svn. The master branch (the trunk in git) has ~ 6500 commits. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Hi, I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? Just to be clear, this has nothing to do with accounts on github, or any registered thing. This is *only* about username/email as recognized by git itself (as recorded in the commit objects). Actually - isn't it better if people do give you their github username / email combo - assuming that's the easiest combo to work with later? Mine is 'matthew-brett' with this (my usual) email address, See you, Matthew ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On 4 June 2010 15:19, Dan Roberts ademan...@gmail.com wrote: Sorry to interrupt, but do you have a usable, up to date cloneable git repository somewhere? I noticed that you had a repository on github, but it's about a month out of date. I understand if what you're working on isn't ready to be cloned from yet. In the meantime I can use git-svn, but I figured if you had something better, I'd use that. This one should be up to date: http://projects.scipy.org/git/numpy.git Regards Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On Wed, Jun 2, 2010 at 3:09 AM, Matthew Brett matthew.br...@gmail.com wrote: Maybe you could put up a list of those people whose emails you need to scrape (obviously without the email addresses) and ask for opt-out? Or opt-in if you think that's better? So here is the list of authors: abaecker alan.mcintyre ariver cdavid chanley charris chris.barker chris.burns christoph.weidemann cookedm darren.dale dhuard dmorrill edschofield ej eric fperez ilan jarrod.millman jmiller joe jswhit kern madhusudancs martin matthew.brett mdroe nobody oliphant patmiller paul.ivanov pearu peridot pierregm prabhu ptvirtan rc rgommers rkern sasha skip stefan test tim_hochberg timl travis travo wfspotz (for wfspotz and matthew.brett, I removed the email suffix). I guess rkern and kern are the same person, as well as travo/oliphant. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Hi. Maybe you could put up a list of those people whose emails you need to scrape (obviously without the email addresses) and ask for opt-out? Or opt-in if you think that's better? So here is the list of authors: Do y'all think opt-in? Or opt-out?If it's opt-in I guess you'll catch most of the current committers, and most of the others you'll lose, but maybe that's good enough. See you, Matthew ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On Wed, Jun 2, 2010 at 10:08 AM, Matthew Brett matthew.br...@gmail.com wrote: Do y'all think opt-in? Or opt-out? If it's opt-in I guess you'll catch most of the current committers, and most of the others you'll lose, but maybe that's good enough. I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? If that is the case, I would really rather avoid this. If someone wants an account on github, they should register an account on their own. Or am I missing something? Thanks, Jarro ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On 06/03/2010 10:24 AM, Jarrod Millman wrote: On Wed, Jun 2, 2010 at 10:08 AM, Matthew Brettmatthew.br...@gmail.com wrote: Do y'all think opt-in? Or opt-out?If it's opt-in I guess you'll catch most of the current committers, and most of the others you'll lose, but maybe that's good enough. I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? Just to be clear, this has nothing to do with accounts on github, or any registered thing. This is *only* about username/email as recognized by git itself (as recorded in the commit objects). Several people already answered me privately to give me their email, I think that's the way to go, cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Technicalities of the SVN - GIT transition
Hi there, I have looked back into the way to convert the existing numpy svn repository into git. It went quite smoothly using svn2git (developed by the KDE team for their own transition), but there are a few questions which need to be answered: - Shall we keep the old svn branches ? I think most of them are just cruft, and can be safely removed We would then just keep the release branches (in maintenance/***) - Tag conversion: svn has no notion of tags, so translating them into git tags cannot be done automatically in a safely manner (and we do have some rewritten tags in the svn repo). I was thinking about creating a small script to create them manually afterwards for the releases, in the svntags/***. - Author conversion: according to git, there are around 50 committers in numpy. Several of them are double and should be be merged I think (kern vs rkern, Travis' accounts as well), but there is also the option to set up real emails. Since email are private, I don't want to just scrape them without asking permission first. I don't know how we should proceed here. The author conversion needs to be decided upfront (as changing name in committers will cause to change every sha256), tags and scrapping branches may be done later. Last time we discussed things, there were some concerns about space: the numpy git repo is around 17 Mb for the full history, 36 Mb if one includes the working tree, compared to 43 Mb for a trunk checkout from svn. The master branch (the trunk in git) has ~ 6500 commits. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Tue, 01 Jun 2010 16:59:47 +0900, David Cournapeau wrote: I have looked back into the way to convert the existing numpy svn repository into git. It went quite smoothly using svn2git (developed by the KDE team for their own transition), but there are a few questions which need to be answered: - Shall we keep the old svn branches ? I think most of them are just cruft, and can be safely removed. We would then just keep the release branches They mostly seem like leftovers and mostly merged to trunk, that's true. At least a prefix svnbranch/** should be added to them, if we are going to keep them at all. Personally, I don't see problems in leaving them out. (in maintenance/***) Why not release/** or releases/**? I'd suggest singular form here. What do other projects use? Does having a prefix here imply something to clones? - Tag conversion: svn has no notion of tags, so translating them into git tags cannot be done automatically in a safely manner (and we do have some rewritten tags in the svn repo). I was thinking about creating a small script to create them manually afterwards for the releases, in the svntags/***. Sounds OK. - Author conversion: according to git, there are around 50 committers in numpy. Several of them are double and should be be merged I think (kern vs rkern, Travis' accounts as well), but there is also the option to set up real emails. Since email are private, I don't want to just scrape them without asking permission first. I don't know how we should proceed here. I don't think correcting the email addresses in the SVN history is very useful. Best probably just use some dummy form, maybe forename.surn...@localhost or something similar to keep things simple. -- Pauli Virtanen ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On 06/01/2010 06:03 PM, Pauli Virtanen wrote: Personally, I don't see problems in leaving them out. (in maintenance/***) Why not release/** or releases/**? Right, release is a better word. Does having a prefix here imply something to clones? Not that I am aware of: it is just that / is allowed in branches, so that gives some nesting, and I think we should have naming conventions for branches. - Tag conversion: svn has no notion of tags, so translating them into git tags cannot be done automatically in a safely manner (and we do have some rewritten tags in the svn repo). I was thinking about creating a small script to create them manually afterwards for the releases, in the svntags/***. Sounds OK. - Author conversion: according to git, there are around 50 committers in numpy. Several of them are double and should be be merged I think (kern vs rkern, Travis' accounts as well), but there is also the option to set up real emails. Since email are private, I don't want to just scrape them without asking permission first. I don't know how we should proceed here. I don't think correcting the email addresses in the SVN history is very useful. Best probably just use some dummy form, maybe That's what svn2git already does, so that would be less work for me :) It may not matter much, but I think there is at least one argument for having real emails: to avoid having duplicate committers (i.e. pvirtanen is the same committer before and after the git transition). But this is only significant for current committers. David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
Hi, I don't think correcting the email addresses in the SVN history is very useful. Best probably just use some dummy form, maybe That's what svn2git already does, so that would be less work for me :) It may not matter much, but I think there is at least one argument for having real emails: to avoid having duplicate committers (i.e. pvirtanen is the same committer before and after the git transition). But this is only significant for current committers. It seems right to try and keep the commit author the same for pre and post SVN commits if possible. Maybe you could put up a list of those people whose emails you need to scrape (obviously without the email addresses) and ask for opt-out? Or opt-in if you think that's better? Thanks for looking into this. Matthew ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
