[leaf-devel] Version Information within the source files
Hi folks Trying to clean up and pull together all the various source and config files I am wondering where the fine version info and modification history within the source files went. Call me old fashioned, but I personally like it. Is that something that just went overboard in the GIT frenzy? cheers Erich smime.p7s Description: S/MIME Cryptographic Signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Version Information within the source files
06.07.2011 09:34, Erich Titl пишет: Hi folks Trying to clean up and pull together all the various source and config files I am wondering where the fine version info and modification history within the source files went. Call me old fashioned, but I personally like it. Is that something that just went overboard in the GIT frenzy? cheers Erich git log --follow path to filename, key '-u' - for view patches. There is no file versions in git, there is a commits - which should be treated as patches. And you even can revert a commit that was done many months ago, without need to apply all fresher modifications manually. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Version Information within the source files
Hi Andrew at 06.07.2011 09:43, Andrew wrote: 06.07.2011 09:34, Erich Titl пишет: Hi folks Trying to clean up and pull together all the various source and config files I am wondering where the fine version info and modification history within the source files went. Call me old fashioned, but I personally like it. Is that something that just went overboard in the GIT frenzy? cheers Erich git log --follow path to filename, key '-u' - for view patches. There is no file versions in git, there is a commits - which should be treated as patches. And you even can revert a commit that was done many months ago, without need to apply all fresher modifications manually. :-) I just like to see individual commit messages within the files, along with some kind of a version, which makes it easier to understand the evolution of the beast. Maybe this is not modern thinking, but then be it. So no chance of including the history automagically into the source as in other version control systems. What a pity. cheers Erich smime.p7s Description: S/MIME Cryptographic Signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Version Information within the source files
Andrew just to show you what I mean commit 1f8bb69aa9b81db2132e3822a21bd6bd879b5cf2 Author: mega m...@luna.think.ch Date: Tue Jun 14 23:49:55 2011 +0200 fixed parsing bug for free memory, probably due to different formatting of the busybox free applet commit 907bb43ddc0dd1c606f79d3920e2488e405a1a55 Author: Andrew Denisenko nitr0...@users.sourceforge.net Date: Thu Jun 23 01:26:02 2011 +0300 Improved clean-up commit 602921c4010c09611b7f499f2ea483058e9f9a0c Author: Andrew Denisenko nitr0...@users.sourceforge.net Date: Thu Jun 23 01:14:50 2011 +0300 Added ipt_netflow commit 2800e41f5918160a328127629efb769086fea1d6 Merge: bff73d6... bfbbc46... Author: Andrew Denisenko nitr0...@users.sourceforge.net Date: Thu Jun 23 00:20:54 2011 +0300 Merge branch 'master' of ssh://leaf.git.sourceforge.net/gitroot/leaf/bering-uclibc commit bff73d651ea13fb58fd5d844cd498c9f66a126d3 Author: Andrew Denisenko nitr0...@users.sourceforge.net Date: Thu Jun 23 00:19:47 2011 +0300 syntax fixes commit bfbbc4603d349f08f75ca1bd12ba7e76941c4de8 Author: Andrew Denisenko nitr0...@users.sourceforge.net Date: Wed Jun 22 23:28:04 2011 +0300 clean-up Most of the above is completely meaningless to the reader, as the commit messages just address the full repository. smime.p7s Description: S/MIME Cryptographic Signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Version Information within the source files
06.07.2011 11:15, Erich Titl пишет: Hi Andrew at 06.07.2011 09:43, Andrew wrote: 06.07.2011 09:34, Erich Titl пишет: Hi folks Trying to clean up and pull together all the various source and config files I am wondering where the fine version info and modification history within the source files went. Call me old fashioned, but I personally like it. Is that something that just went overboard in the GIT frenzy? cheers Erich git log --followpath to filename, key '-u' - for view patches. There is no file versions in git, there is a commits - which should be treated as patches. And you even can revert a commit that was done many months ago, without need to apply all fresher modifications manually. :-) I just like to see individual commit messages within the files, along with some kind of a version, which makes it easier to understand the evolution of the beast. Maybe this is not modern thinking, but then be it. There is no need for individual commits for each file - one commit can touch unlimited number of files. This is much better than individual commits - at least, there is no problem to rollback to any state of repository - to tag commit or to start new branch. There are some kind of 'version' - files hash (that can be seen in output of `git log -u`), but it's better to treat versions as commits hash. So no chance of including the history automagically into the source as in other version control systems. What a pity. cheers Erich -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Version Information within the source files
06.07.2011 11:21, Erich Titl пишет: Most of the above is completely meaningless to the reader, as the commit messages just address the full repository. You can see commits that affects some file (git log --follow path/to/file.name), and if messages are too generic - '-u' option will help you to see what was really changed. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
