Menu
▾
▴
Re: [E1000-devel] e1000e driver ChangeLog?
|
From: Ronciak, J. <joh...@in...> - 2010-03-31 17:26:07
|
>The standard open-source project methodology is to include a >'ChangeLog' >text file in the driver source tree which contains a >cumulative history >of the changes for a given driver by version. We aren't doing this now but we used to. We stopped as it didn't seem to be of much use and got that same feedback from consumers of our drivers. This was a long time ago so we'll take this under advisement within the team. We'll see if we can't do something like this. Upstream kernel files used to have something similar but it isn't done there either. The SCM system is used for that type of tracking. You could use git btw as we try to keep the versions fairly close to each other. Cheers, John ----------------------------------------------------------- "...that your people will judge you on what you can build, not what you destroy.", B. Obama, 2009 >-----Original Message----- >From: Andy Cress [mailto:and...@us...] >Sent: Wednesday, March 31, 2010 10:01 AM >To: Ronciak, John; E10...@li... >Subject: RE: [E1000-devel] e1000e driver ChangeLog? > >John, > >Thanks for your reply. I did see Jesse's reply after checking my >filters. I don't think this is an issue with sourceforge, since many >other projects do not have this issue. The ReleaseNotes files that are >posted with some of the driver releases are helpful, but commonly the >use case is: > - Problem X is noticed, and we need to see if it is already fixed in a >later driver > - There are several/many releases that have occurred since the version >of the driver that > is seeing problem X > - This requires collecting many of the ReleaseNotes files and >searching >through each of them, > but not all releases are posted with ReleaseNotes. And frequently >problem X is not described > in the resulting files. > - Now I go through and do a search of the bugzillas and email list >archives and find through > email that problem X has had several patches applied for it, but >those are not included in > any of the ReleaseNotes. > >The standard open-source project methodology is to include a >'ChangeLog' >text file in the driver source tree which contains a >cumulative history >of the changes for a given driver by version. >And whenever source changes/patches are made, some notation goes into >'ChangeLog'. >If that isn't already implemented it would seem like a good idea going >forward, and I'm sure that there are many others who would benefit. > >Andy > >-----Original Message----- >From: Ronciak, John [mailto:joh...@in...] >Sent: Wednesday, March 31, 2010 12:20 PM >To: Andy Cress; E10...@li... >Subject: [SPAM] - RE: [E1000-devel] e1000e driver ChangeLog? - Email >found in subject > >I think Jesse replied to this but in case you didn't see that for some >reason here it is again. > >The new Sourceforge site has made it hard to link the logs to the >drivers as they are posted. The logs are there as a separate file >located with the driver. Please look at those files to see if this is >what you are looking for. There seem to be a few missing but we think >this has to do with the SF site and not us putting them up there. > >Hopefully the SF will get better regarding this but it will probably >take time. We are pushing on them to fix things. > >Cheers, >John >----------------------------------------------------------- >"...that your people will judge you on what you can build, not what you >destroy.", B. Obama, 2009 > > > >>-----Original Message----- >>From: Andy Cress [mailto:and...@us...] >>Sent: Wednesday, March 31, 2010 6:41 AM >>To: E10...@li... >>Subject: Re: [E1000-devel] e1000e driver ChangeLog? >> >>I haven't seen a response yet. Is there a ChangeLog for the e1000 >>project at all? >>If not, how do the driver updates get submitted to kernel.org? >>It seems like this information has to exist somewhere in the >project. >> >>Andy >> >>-----Original Message----- >>From: Andy Cress [mailto:and...@us...] >>Sent: Monday, March 22, 2010 10:01 AM >>To: E10...@li... >>Subject: [E1000-devel] e1000e driver ChangeLog? >> >> >>In the files/, there is occasionally a release.txt file with some >>incremental changes listed, but I don't see a ChangeLog for the e1000e >>driver. Where could I find that? >> >>Andy >> >> >> >> >> >>--------------------------------------------------------------- >>--------------- >>Download Intel® Parallel Studio Eval >>Try the new software tools for yourself. Speed compiling, find bugs >>proactively, and fine-tune applications for parallel performance. >>See why Intel Parallel Studio got high marks during beta. >>http://p.sf.net/sfu/intel-sw-dev >>_______________________________________________ >>E1000-devel mailing list >>E10...@li... >>https://lists.sourceforge.net/lists/listinfo/e1000-devel >>To learn more about Intel® Ethernet, visit >>http://communities.intel.com/community/wired >>mmunity/wired >> > > > |
