From: William C. <wc...@re...> - 2011-01-03 16:28:31
|
Hi All, The OProfile source repository is currently CVS-based. I have been using git more lately because I have found git pretty convenient. Looking around the web I found some instructions on using CVS repository with a local git repository: http://drupal.org/node/288873 I thought other people working on OProfile might also be interested in using git for their local repository. I did some minor tweaks on the commands to use environment variables to minimize typing. You will need to adjust the environment variables for local conditions. Below are the commands used to setup a local and use a local OProfile git repository. -Will Environment variable setup: export CVSROOT=:ext:USE...@op...:/cvsroot/oprofile export MODULE_NAME=oprofile export GIT_CVS_CLONE=~/oprofile/oprofile.git export CVS_WC_MODULE=~/oprofile/oprofile export WORKING_SAND_BOX=~/oprofile/oprofile.work.git Importing your module's CVS tree cvs login mkdir $GIT_CVS_CLONE cd $GIT_CVS_CLONE git cvsimport -a -p -x -v -d $CVSROOT $MODULE_NAME Creating your workplace mkdir $WORKING_SAND_BOX cd $WORKING_SAND_BOX git clone -l $GIT_CVS_CLONE $MODULE_NAME Updating git repo cd $GIT_CVS_CLONE git cvsimport -a -p -x -v -d $CVSROOT $MODULE_NAME And update our working sandbox accordingly... cd $WORKING_SAND_BOX/$MODULE_NAME git fetch git rebase origin/HEAD commits from git to cvs: cd $WORKING_SAND_BOX/$MODULE_NAME git log git cvsexportcommit -c -v -u -p -w $CVS_WC_MODULE <commit-sha1> |
From: John V. <jvi...@re...> - 2011-01-03 16:41:33
|
Maynard, Since you are the maintainer for the Oprofile userspace package. What are your thoughts on moving over to Git at some point during 2011? I would really like it if we did :) Thanks, John -- John Villalovos Intel Corporation on-site partner engineer at Red Hat, Inc. http://tabasco.usersys.redhat.com/ |
From: Maynard J. <may...@us...> - 2011-01-05 17:24:24
|
John Villalovos wrote: > Maynard, > > Since you are the maintainer for the Oprofile userspace package. > > What are your thoughts on moving over to Git at some point during 2011? Unless someone can make a case that this is really needed for the overall oprofile community's benefit, it'll be on my back burner until I have nothing more important to do. If you like using a git repo for your local work, it seems that Will's Jan 3 posting ("Using a local git repository with OProfile CVS") is the solution for now. -Maynard > I would really like it if we did :) > > Thanks, > John > |
From: James J. D. <jam...@gm...> - 2011-01-10 13:33:38
Attachments:
signature.asc
|
On 01/05/2011 11:22 PM, John Villalovos wrote: > On 1/5/2011 12:24 PM, Maynard Johnson wrote: >> John Villalovos wrote: >>> Maynard, >>> >>> Since you are the maintainer for the Oprofile userspace package. >>> >>> What are your thoughts on moving over to Git at some point during 2011? >> Unless someone can make a case that this is really needed for the overall oprofile community's benefit, it'll be on my back burner until I have nothing more important to do. If you like using a git repo for your local work, it seems that Will's Jan 3 posting ("Using a local git repository with OProfile CVS") is the solution for now. > > The only case that I have is that I think it would improve development. > > I'm guessing quite a few of the people who would contribute to oprofile > development are kernel developers. Since they are already using git > then it makes it easier for them to also contribute to the userspace > code. A common source control tool for the userspace and kernel > component seems to make sense. And since we know that the kernel won't > be switching to CVS, it would require the userspace to switch to git in > order to have a common source control tool for both pieces. OK. There is a bit of a catch 22 here, as people who understand git are much less likely to contribute to oprofile, and so their opinions are likely to be seen as invalid. After all, I'm piping up with an opinion, and I never contributed anyway, so who needs me, right!!??? I can tell you that I don't bother to try to contribute to any projects that use CVS or Subversion as their SCM tools. It is 2011, and there is just no argument for using them that doesn't boil down to "I would rather use broken tools for the foreseeable future, and force everyone else to do the same, than take a few hours to learn how to do SCM right and use git." To be fair, those people usually don't understand that CVS and Subversion are NOT just equivalent tools to git using different command syntax. They really believe it is just six of one or a half dozen of the other. If that was the case Linus' would have just used Subversion, but he didn't of course (see also http://www.youtube.com/watch?v=4XpnKHJAok8 ) Well, I suspect I haven't made many friends with my first post here, but I'll take the bullet for all the people who agree but don't want the ill will that can often accompany disagreeing with the project maintainer :-) <snip> > Thanks, > John > |
From: John L. <le...@mo...> - 2011-01-10 15:44:35
|
On Mon, Jan 10, 2011 at 08:28:31AM -0500, James J. Dines wrote: > likely to be seen as invalid. After all, I'm piping up with an opinion, > and I never contributed anyway, so who needs me, right!!??? Indeed. john |
From: John V. <jvi...@re...> - 2011-01-06 04:22:29
|
On 1/5/2011 12:24 PM, Maynard Johnson wrote: > John Villalovos wrote: >> Maynard, >> >> Since you are the maintainer for the Oprofile userspace package. >> >> What are your thoughts on moving over to Git at some point during 2011? > Unless someone can make a case that this is really needed for the overall oprofile community's benefit, it'll be on my back burner until I have nothing more important to do. If you like using a git repo for your local work, it seems that Will's Jan 3 posting ("Using a local git repository with OProfile CVS") is the solution for now. The only case that I have is that I think it would improve development. I'm guessing quite a few of the people who would contribute to oprofile development are kernel developers. Since they are already using git then it makes it easier for them to also contribute to the userspace code. A common source control tool for the userspace and kernel component seems to make sense. And since we know that the kernel won't be switching to CVS, it would require the userspace to switch to git in order to have a common source control tool for both pieces. On a personal note. I haven't used CVS in years and had to re-acquaint myself with it to work on submitting some patches. And I expect others may have that same issue if they also haven't used CVS in years, since we tend to forget what was once 2nd nature. I personally believe that switching to git would be to the overall oprofile community's benefit. But maybe there are arguments against. I have heard other people express interest in git for the userspace. One alternative might be to initially create an official git repository that is kept continually in sync with the CVS tree. That would be quite helpful to me and hopefully others. Thanks, John -- John Villalovos An Intel Corporation employee on assignment at Red Hat as an on-site partner engineer. |
From: William C. <wc...@re...> - 2011-01-31 20:44:23
Attachments:
oprofile.options
|
Hi All, Given the that CVS is currently shutdown for sourceforge and it is unclear when it is going to be restored I took another look at converting the repository to git. I ended up using cvs2git to handle the mapping of authors of cvs commits. The conversion was based on information from the following links: http://michael-bien.com/mbien/entry/converting_from_cvs_to_git http://cvs2svn.tigris.org/cvs2git.html http://sourceforge.net/apps/trac/sourceforge/wiki/CVS#Backups The first step is to have a local rsync version of cvs repositories. I had done the following steps a couple weeks around Janaury 10, 2011 before the sourceforge CVS shutdown, and there is one entry missing from January 17, 2011. The steps were for generation of the local cvs repo were: mkdir sourceforge cd sourceforge/ #the following probably won't work with sourceforge cvs shutdown now rsync -av rsync://oprofile.cvs.sourceforge.net/cvsroot/oprofile/* . Once the local cvs repository has been set up I used the cvs2git script with oprofile.options file to produce the needed git file: cvs2git --options=oprofile.options --fallback-encoding=utf_8 mkdir gitrepo cd gitrepo git init cat ../cvs2svn-tmp/git-blob.dat ../cvs2svn-tmp/git-dump.dat | git fast-import git checkout master At this point I have a local git repository for oprofile. I followed the instructions for pushing a git repo to sourceforge with the instructions at: http://sourceforge.net/apps/trac/sourceforge/wiki/Git The previous URL also describes how to download the repo. You should be able to browse the git repo at: http://oprofile.git.sourceforge.net/git/gitweb-index.cgi This should mirror what was in the cvs repository with the exception it is currently missing the following cvs checkin: 2011-01-17 Will Deacon <wil...@ar...> * events/arm/armv7-ca9/events: Add missing TLB event -Will |
From: Maynard J. <may...@us...> - 2011-02-01 14:52:05
|
William Cohen wrote: > Hi All, Will, Thanks much for these tips. I guess I may need to act on this sooner rather than later. From the Jan 29 SF blog entry (http://sourceforge.net/blog/) . . . "We are also considering the end-of-life of the CVS service and hope to have user support in migrating CVS users to Subversion in coming months. Subversion generally provides parity to CVS commands, and many of our users have made this transition successfully in the past. From SVN, projects can move to Git if desired." I have a lot on my plate right now with other non-oprofile responsibilities, so it may be a couple months before I can effect this change. But change is coming, and I'll try to stay ahead of the bow wave. -Maynard > > Given the that CVS is currently shutdown for sourceforge and it is > unclear when it is going to be restored I took another look at > converting the repository to git. I ended up using cvs2git to handle > the mapping of authors of cvs commits. The conversion was based on > information from the following links: > > http://michael-bien.com/mbien/entry/converting_from_cvs_to_git > http://cvs2svn.tigris.org/cvs2git.html > http://sourceforge.net/apps/trac/sourceforge/wiki/CVS#Backups > > The first step is to have a local rsync version of cvs repositories. I > had done the following steps a couple weeks around Janaury 10, 2011 > before the sourceforge CVS shutdown, and there is one entry missing > from January 17, 2011. The steps were for generation of the local cvs > repo were: > > mkdir sourceforge > cd sourceforge/ > #the following probably won't work with sourceforge cvs shutdown now > rsync -av rsync://oprofile.cvs.sourceforge.net/cvsroot/oprofile/* . > > Once the local cvs repository has been set up I used the cvs2git > script with oprofile.options file to produce the needed git file: > > cvs2git --options=oprofile.options --fallback-encoding=utf_8 > mkdir gitrepo > cd gitrepo > git init > cat ../cvs2svn-tmp/git-blob.dat ../cvs2svn-tmp/git-dump.dat | git fast-import > git checkout master > > At this point I have a local git repository for oprofile. I followed the instructions for > pushing a git repo to sourceforge with the instructions at: > > http://sourceforge.net/apps/trac/sourceforge/wiki/Git > > The previous URL also describes how to download the repo. You should > be able to browse the git repo at: > > http://oprofile.git.sourceforge.net/git/gitweb-index.cgi > > This should mirror what was in the cvs repository with the exception it > is currently missing the following cvs checkin: > > 2011-01-17 Will Deacon <wil...@ar...> > > * events/arm/armv7-ca9/events: Add missing TLB event > > > -Will > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > > > > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: William C. <wc...@re...> - 2011-02-01 15:22:50
|
On 02/01/2011 09:52 AM, Maynard Johnson wrote: > William Cohen wrote: >> Hi All, > Will, > Thanks much for these tips. I guess I may need to act on this sooner rather than later. From the Jan 29 SF blog entry (http://sourceforge.net/blog/) . . . > > "We are also considering the end-of-life of the CVS service > and hope to have user support in migrating CVS users to > Subversion in coming months. Subversion generally provides > parity to CVS commands, and many of our users have made this > transition successfully in the past. > > From SVN, projects can move to Git if desired." > > I have a lot on my plate right now with other non-oprofile responsibilities, so it may be a couple months before I can effect this change. But change is coming, and I'll try to stay ahead of the bow wave. > > -Maynard Hi Maynard, I understand having to switch between a variety of tasks, so it is understandable if you don't have much time at the moment to deal with this. I have only moved the oprofile code repository over to git. I haven't dealt with the other oprofile cvs repositories (oprofile-results, oprofile-tests, and oprofile-www). The Oprofile git repo for the code is live right now. You should be able to down load it by replacing "USERNAME" with your sourceforge login: git clone ssh://USE...@op.../gitroot/oprofile/oprofile SystemTap had a similar migration from cvs to git. One thing that was done to make merging easier was to eliminate the explicit changelog file; it resulted in many conflicts. All that information in the changelog can be easily obtained from "git log". -Will |
From: William C. <wc...@re...> - 2011-02-01 16:29:51
|
On 02/01/2011 10:22 AM, William Cohen wrote: > On 02/01/2011 09:52 AM, Maynard Johnson wrote: >> William Cohen wrote: >>> Hi All, >> Will, >> Thanks much for these tips. I guess I may need to act on this sooner rather than later. From the Jan 29 SF blog entry (http://sourceforge.net/blog/) . . . >> >> "We are also considering the end-of-life of the CVS service >> and hope to have user support in migrating CVS users to >> Subversion in coming months. Subversion generally provides >> parity to CVS commands, and many of our users have made this >> transition successfully in the past. >> >> From SVN, projects can move to Git if desired." >> >> I have a lot on my plate right now with other non-oprofile responsibilities, so it may be a couple months before I can effect this change. But change is coming, and I'll try to stay ahead of the bow wave. >> >> -Maynard > > Hi Maynard, > > I understand having to switch between a variety of tasks, so it is understandable if you don't have much time at the moment to deal with this. I have only moved the oprofile code repository over to git. I haven't dealt with the other oprofile cvs repositories (oprofile-results, oprofile-tests, and oprofile-www). > > The Oprofile git repo for the code is live right now. You should be able to down load it by replacing "USERNAME" with your sourceforge login: > > git clone ssh://USE...@op.../gitroot/oprofile/oprofile > > > SystemTap had a similar migration from cvs to git. One thing that was done to make merging easier was to eliminate the explicit changelog file; it resulted in many conflicts. All that information in the changelog can be easily obtained from "git log". > > -Will I took a look at porting over oprofile-tests and oprofile-results CVS repositories this morning. Can't do those right now because according to http://sourceforge.net/apps/trac/sourceforge/wiki/Git#CreatingMultipleRepositories I need to use a shell to set up the additional directories. -Will |
From: Maynard J. <may...@us...> - 2011-02-01 16:47:40
|
William Cohen wrote: > On 02/01/2011 10:22 AM, William Cohen wrote: >> On 02/01/2011 09:52 AM, Maynard Johnson wrote: >>> William Cohen wrote: >>>> Hi All, >>> Will, >>> Thanks much for these tips. I guess I may need to act on this sooner rather than later. From the Jan 29 SF blog entry (http://sourceforge.net/blog/) . . . >>> >>> "We are also considering the end-of-life of the CVS service >>> and hope to have user support in migrating CVS users to >>> Subversion in coming months. Subversion generally provides >>> parity to CVS commands, and many of our users have made this >>> transition successfully in the past. >>> >>> From SVN, projects can move to Git if desired." >>> >>> I have a lot on my plate right now with other non-oprofile responsibilities, so it may be a couple months before I can effect this change. But change is coming, and I'll try to stay ahead of the bow wave. >>> >>> -Maynard >> >> Hi Maynard, >> >> I understand having to switch between a variety of tasks, so it is understandable if you don't have much time at the moment to deal with this. I have only moved the oprofile code repository over to git. I haven't dealt with the other oprofile cvs repositories (oprofile-results, oprofile-tests, and oprofile-www). >> >> The Oprofile git repo for the code is live right now. You should be able to down load it by replacing "USERNAME" with your sourceforge login: >> >> git clone ssh://USE...@op.../gitroot/oprofile/oprofile >> >> >> SystemTap had a similar migration from cvs to git. One thing that was done to make merging easier was to eliminate the explicit changelog file; it resulted in many conflicts. All that information in the changelog can be easily obtained from "git log". >> >> -Will > > I took a look at porting over oprofile-tests and oprofile-results CVS repositories this morning. Can't do those right now because according to http://sourceforge.net/apps/trac/sourceforge/wiki/Git#CreatingMultipleRepositories I need to use a shell to set up the additional directories. Ah, evidently I misunderstood your initial message. I guess I skimmed through it too fast. I thought you couldn't actually execute the migration to git due to cvs being down. Anyway, I'll take a look at migrating the other directories to git when I have time. For now, though, I presume users will still be able to download oprofile using the cvs command specified at http://oprofile.sourceforge.net/download/. I'll update those download instructions once the switch-over to git is complete. -Maynard > > -Will > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: William C. <wc...@re...> - 2011-02-01 17:09:44
|
On 02/01/2011 11:48 AM, Maynard Johnson wrote: > William Cohen wrote: >> I took a look at porting over oprofile-tests and oprofile-results CVS repositories this morning. Can't do those right now because according to http://sourceforge.net/apps/trac/sourceforge/wiki/Git#CreatingMultipleRepositories I need to use a shell to set up the additional directories. > > Ah, evidently I misunderstood your initial message. I guess I skimmed through it too fast. I thought you couldn't actually execute the migration to git due to cvs being down. Anyway, I'll take a look at migrating the other directories to git when I have time. For now, though, I presume users will still be able to download oprofile using the cvs command specified at http://oprofile.sourceforge.net/download/. I'll update those download instructions once the switch-over to git is complete. I lucked out on the migration because I had an recent rsynced version of the CVS files sitting around. When I tried to checkout following the instructions on: http://oprofile.sourceforge.net/download/ I got the following: $ export CVSROOT=":pserver:ano...@op...:/cvsroot/oprofile" cvs login $ cvs -z3 co oprofile cvs [checkout aborted]: connect to [oprofile.cvs.sourceforge.net]:2401 failed: Connection refused So right now it is the tar.gz files or git repository. No CVS at all. -Will > > -Maynard >> >> -Will >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> oprofile-list mailing list >> opr...@li... >> https://lists.sourceforge.net/lists/listinfo/oprofile-list > |
From: Maynard J. <may...@us...> - 2011-02-01 17:26:01
|
William Cohen wrote: > On 02/01/2011 11:48 AM, Maynard Johnson wrote: >> William Cohen wrote: > >>> I took a look at porting over oprofile-tests and oprofile-results CVS repositories this morning. Can't do those right now because according to http://sourceforge.net/apps/trac/sourceforge/wiki/Git#CreatingMultipleRepositories I need to use a shell to set up the additional directories. >> >> Ah, evidently I misunderstood your initial message. I guess I skimmed through it too fast. I thought you couldn't actually execute the migration to git due to cvs being down. Anyway, I'll take a look at migrating the other directories to git when I have time. For now, though, I presume users will still be able to download oprofile using the cvs command specified at http://oprofile.sourceforge.net/download/. I'll update those download instructions once the switch-over to git is complete. > > I lucked out on the migration because I had an recent rsynced version of the CVS files sitting around. When I tried to checkout following the instructions on: > > http://oprofile.sourceforge.net/download/ > > I got the following: > > $ export CVSROOT=":pserver:ano...@op...:/cvsroot/oprofile" cvs login > $ cvs -z3 co oprofile > cvs [checkout aborted]: connect to [oprofile.cvs.sourceforge.net]:2401 failed: Connection refused > > So right now it is the tar.gz files or git repository. No CVS at all. Right, the SF blog posting said it would probably be late week before cvs service is restore. -Maynard > > -Will > > >> >> -Maynard >>> >>> -Will >>> >>> ------------------------------------------------------------------------------ >>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >>> Finally, a world-class log management solution at an even better price-free! >>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >>> February 28th, so secure your free ArcSight Logger TODAY! >>> http://p.sf.net/sfu/arcsight-sfd2d >>> _______________________________________________ >>> oprofile-list mailing list >>> opr...@li... >>> https://lists.sourceforge.net/lists/listinfo/oprofile-list >> > |
From: William C. <wc...@re...> - 2011-02-10 20:59:09
|
On 02/01/2011 12:26 PM, Maynard Johnson wrote: > William Cohen wrote: >> So right now it is the tar.gz files or git repository. No CVS at all. > Right, the SF blog posting said it would probably be late week before cvs service is restore. > > -Maynard Hi Maynard, sourceforge has turned on cvs and shell services back on. This has made it possible to add git repos for the other oprofile cvs repositories (oprofile-results and oprofile-tests) to: http://oprofile.git.sourceforge.net/git/gitweb-index.cgi They can be cloned with the following: git clone git://oprofile.git.sourceforge.net/gitroot/oprofile/oprofile-results git clone git://oprofile.git.sourceforge.net/gitroot/oprofile/oprofile-tests More information about using sourceforge git repositories is at: https://sourceforge.net/apps/trac/sourceforge/wiki/Git I know there were a several people include myself that would prefer to use git rather than CVS. We already have the git repos set up so it would be easy to point people at using the git repos. We would need to make some updates to the oprofile webpages for the repos to mention those new locations. The oprofile webpages are also stored in CVS. I have been able to convert those into a local git repository, but I am not sure how to properly push those back to the website so changes in the git repo are visible on the website. -Will |
From: William C. <wc...@re...> - 2011-02-11 16:20:47
|
Hi All, I have made git versions of the four oprofile CVS repositories (oprofile, oprofile-results, oprofile-tests, and oprofile-www). The are browsable at http://oprofile.git.sourceforge.net/git/gitweb-index.cgi. At this point it would be very little additional work to complete the switch from cvs to git. The remain work would to switch would be: 1) Change instructions on ./download/index.php for downloading/contributing 2) Update release checklist. 3) Change opr...@li... to note git commits The advantages to using git would include 1) code repository that system kernel developers are comfortable with 2) decentralized code repository 3) people would be able to have local repositories for their changes/development What are peoples comments on completing the switch to git? -Will |
From: Lind, P. <pl...@mi...> - 2011-02-11 18:41:57
|
Hi Will -- Thank you very much for advocating this and pushing forward with it. I would strongly support completing the switch to git. I don't know how my "my vote" for this will count, since I have only submitted a single patch to oprofile. But I hope to submit more in the future. As others have previously posted, there are many advantages to working with git. There is a bit of a learning curve, but once you "get it", it becomes a far more powerful tool for working with your code. One thing that can be off-putting to new users is the sheer amount of flexibility that git offers. (Why do I want de-centralized repos? How do I use all these branches that are so easy to create? Should we have multiple branches on the sourceforge server? Why or why not?) Maybe it would help to have a short section on the wiki page on "git best practices" specifically for oprofile. Also, maybe a short list of git web docs to read. There are so many online git resources these days, that one may not know where to start. (I like these: http://progit.org/book/ and http://book.git-scm.com/) I could help a bit with doc writing, but I don't really know the current oprofile maintainer workflow. I just mailed in my patch :-) If someone gives me a few clues, I could try and write something up. Thanks, paul On 2/11/11 8:20 AM, "William Cohen" <wc...@re...> wrote: >Hi All, > >I have made git versions of the four oprofile CVS repositories (oprofile, >oprofile-results, oprofile-tests, and oprofile-www). The are browsable at >http://oprofile.git.sourceforge.net/git/gitweb-index.cgi. At this point >it would be very little additional work to complete the switch from cvs >to git. > >The remain work would to switch would be: >1) Change instructions on ./download/index.php for >downloading/contributing >2) Update release checklist. >3) Change opr...@li... to note git commits > >The advantages to using git would include > >1) code repository that system kernel developers are comfortable with >2) decentralized code repository >3) people would be able to have local repositories for their >changes/development > >What are peoples comments on completing the switch to git? > >-Will > > > >-------------------------------------------------------------------------- >---- >The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >Pinpoint memory and threading errors before they happen. >Find and fix more than 250 security defects in the development cycle. >Locate bottlenecks in serial and parallel code that limit performance. >http://p.sf.net/sfu/intel-dev2devfeb >_______________________________________________ >oprofile-list mailing list >opr...@li... >https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: William C. <wc...@re...> - 2011-02-14 15:32:17
|
On 02/11/2011 01:05 PM, Lind, Paul wrote: > Hi Will -- > > Thank you very much for advocating this and pushing forward with it. > > I would strongly support completing the switch to git. > > I don't know how my "my vote" for this will count, since I have only > submitted a single patch to oprofile. But I hope to submit more in the > future. > > As others have previously posted, there are many advantages to working > with git. There is a bit of a learning curve, but once you "get it", it > becomes a far more powerful tool for working with your code. > > One thing that can be off-putting to new users is the sheer amount of > flexibility that git offers. (Why do I want de-centralized repos? How do I > use all these branches that are so easy to create? Should we have multiple > branches on the sourceforge server? Why or why not?) > > Maybe it would help to have a short section on the wiki page on "git best > practices" specifically for oprofile. > > Also, maybe a short list of git web docs to read. There are so many online > git resources these days, that one may not know where to start. (I like > these: http://progit.org/book/ and http://book.git-scm.com/) > > I could help a bit with doc writing, but I don't really know the current > oprofile maintainer workflow. I just mailed in my patch :-) If someone > gives me a few clues, I could try and write something up. > > Thanks, > > paul Hi Paul, I would like to switch over to git. There have been other people that have interested in using git for oprofile's code repository, but I would like to make sure there is consensus for doing the switch to git. I encountered the cvs to git migration before and there was some learning required. It might be useful to have a cookbook in the oprofile-www with the following recipes: 0) How to creat initial local git tree and keep it up to date 1) How to create the patch locally 2) How to submit patch inclusion upstream (update http://oprofile.sourceforge.net/contribute/) -Will |
From: Maynard J. <may...@us...> - 2011-02-15 14:47:12
|
William Cohen wrote: > On 02/11/2011 01:05 PM, Lind, Paul wrote: >> Hi Will -- >> >> Thank you very much for advocating this and pushing forward with it. >> >> I would strongly support completing the switch to git. >> >> I don't know how my "my vote" for this will count, since I have only >> submitted a single patch to oprofile. But I hope to submit more in the >> future. >> >> As others have previously posted, there are many advantages to working >> with git. There is a bit of a learning curve, but once you "get it", it >> becomes a far more powerful tool for working with your code. >> >> One thing that can be off-putting to new users is the sheer amount of >> flexibility that git offers. (Why do I want de-centralized repos? How do I >> use all these branches that are so easy to create? Should we have multiple >> branches on the sourceforge server? Why or why not?) >> >> Maybe it would help to have a short section on the wiki page on "git best >> practices" specifically for oprofile. >> >> Also, maybe a short list of git web docs to read. There are so many online >> git resources these days, that one may not know where to start. (I like >> these: http://progit.org/book/ and http://book.git-scm.com/) >> >> I could help a bit with doc writing, but I don't really know the current >> oprofile maintainer workflow. I just mailed in my patch :-) If someone >> gives me a few clues, I could try and write something up. >> >> Thanks, >> >> paul > > Hi Paul, > > I would like to switch over to git. There have been other people that have interested in using git for oprofile's code repository, but I would like to make sure there is consensus for doing the switch to git. > > I encountered the cvs to git migration before and there was some learning required. It might be useful to have a cookbook in the oprofile-www with the following recipes: > > 0) How to creat initial local git tree and keep it up to date > 1) How to create the patch locally > 2) How to submit patch inclusion upstream (update http://oprofile.sourceforge.net/contribute/) Paul, Thanks for the doc-writing offer! Will has some great suggestions. If you write something up, I'll handle putting it in the right place on the oprofile SF website. Just write in text format -- I'll take care of web'izing it. Due to other non-oprofile matters, it may be a few weeks before I can spend the day or so to make the official switch-over to git. -Maynard > > -Will > > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: William C. <wc...@re...> - 2011-02-15 15:31:20
Attachments:
download.diff
|
On 02/15/2011 09:47 AM, Maynard Johnson wrote: > William Cohen wrote: >> On 02/11/2011 01:05 PM, Lind, Paul wrote: >>> Hi Will -- >>> >>> Thank you very much for advocating this and pushing forward with it. >>> >>> I would strongly support completing the switch to git. >>> >>> I don't know how my "my vote" for this will count, since I have only >>> submitted a single patch to oprofile. But I hope to submit more in the >>> future. >>> >>> As others have previously posted, there are many advantages to working >>> with git. There is a bit of a learning curve, but once you "get it", it >>> becomes a far more powerful tool for working with your code. >>> >>> One thing that can be off-putting to new users is the sheer amount of >>> flexibility that git offers. (Why do I want de-centralized repos? How do I >>> use all these branches that are so easy to create? Should we have multiple >>> branches on the sourceforge server? Why or why not?) >>> >>> Maybe it would help to have a short section on the wiki page on "git best >>> practices" specifically for oprofile. >>> >>> Also, maybe a short list of git web docs to read. There are so many online >>> git resources these days, that one may not know where to start. (I like >>> these: http://progit.org/book/ and http://book.git-scm.com/) >>> >>> I could help a bit with doc writing, but I don't really know the current >>> oprofile maintainer workflow. I just mailed in my patch :-) If someone >>> gives me a few clues, I could try and write something up. >>> >>> Thanks, >>> >>> paul >> >> Hi Paul, >> >> I would like to switch over to git. There have been other people that have interested in using git for oprofile's code repository, but I would like to make sure there is consensus for doing the switch to git. >> >> I encountered the cvs to git migration before and there was some learning required. It might be useful to have a cookbook in the oprofile-www with the following recipes: >> >> 0) How to creat initial local git tree and keep it up to date >> 1) How to create the patch locally >> 2) How to submit patch inclusion upstream (update http://oprofile.sourceforge.net/contribute/) > Paul, > Thanks for the doc-writing offer! Will has some great suggestions. If you write something up, I'll handle putting it in the right place on the oprofile SF website. Just write in text format -- I'll take care of web'izing it. > > Due to other non-oprofile matters, it may be a few weeks before I can spend the day or so to make the official switch-over to git. > > -Maynard Hi Maynard, If it will speed up the process, I am also willing to further help with the switch over git by doing some web page updates. I do have the ability to update the OProfile webpages. Attached is a mininal patch to oprofile-www for dowloading things with git. Sign-off-by: William Cohen <wc...@re...> 2011-02-15 William Cohen <wc...@re...> * start_page.php: * download/index.php: Point to git repositories. -Will |
From: John L. <le...@mo...> - 2011-02-01 16:47:00
|
On Tue, Feb 01, 2011 at 10:22:41AM -0500, William Cohen wrote: > SystemTap had a similar migration from cvs to git. One thing that was > done to make merging easier was to eliminate the explicit changelog > file; it resulted in many conflicts. All that information in the > changelog can be easily obtained from "git log". We originally had a ChangeLog file because CVS was so crappy about digging through historical data. That's obviously not the case with git so that makes sense to me (and course there's no need to list the author, date, email, or files changed explicitly in this case either) regards john |