Foss lect 8 1 11.txt - Revision history

Missing actor at 07:58, 11 February 2011

2011-02-11T07:58:14Z

← Older revision		Revision as of 13:28, 11 February 2011
Line 83:		Line 83:

	----		----

			'''Commands to be used for Git'''


			git commit -a: where a indicates all

			git log

			git init

			git add

			git diff

			git branch

			git checkout branch

			git whatchanged

			eg: git whatchanged since="may 2010"

			git status: Shows the log messages

			git clone





	~~Homework for the week~~		~~Homework for the week~~

Missing actor at 11:44, 18 January 2011

2011-01-18T11:44:31Z

← Older revision		Revision as of 17:14, 18 January 2011
Line 42:		Line 42:
	In git you cannot recover an older version unless it is branched out. If the reversion is done		In git you cannot recover an older version unless it is branched out. If the reversion is done
	on the trunk, the new stuff is lost. No version numbers in git.		on the trunk, the new stuff is lost. No version numbers in git.

			For practicing the remote git repository go to [https://github.com/ git hub] you can create and play with the remote git repository.
			You have to create the account there. You can go through the help documents on that site also for any problem.

	Upstream/downstream concept: A developer who fixes a bug in a software obtained from the community		Upstream/downstream concept: A developer who fixes a bug in a software obtained from the community

Missing actor at 12:25, 15 January 2011

2011-01-15T12:25:05Z

← Older revision		Revision as of 17:55, 15 January 2011
Line 73:		Line 73:
	Then we can enter for e.g. function which we want to find, in which file it is? after entering function name, press enter.		Then we can enter for e.g. function which we want to find, in which file it is? after entering function name, press enter.
	Cscope will list the names of files in which it has found that function. We can go through that file by pressing enter on that file name.		Cscope will list the names of files in which it has found that function. We can go through that file by pressing enter on that file name.

	Hyphenation Session by Shravan:		Hyphenation Session by Shravan:
	Hyphenation dictionary has all the rules.		Hyphenation dictionary has all the rules.

Missing actor at 12:23, 15 January 2011

2011-01-15T12:23:52Z

← Older revision		Revision as of 17:53, 15 January 2011
Line 71:		Line 71:
	Then actual code browsing can be done using cscope.		Then actual code browsing can be done using cscope.
	$scope		$scope
	Then we can enter for e.g. function which we want to find, in which file it is? after entering function name, press enter. Cscope will list the names of files in which it has found that function. We can go through that file by pressing enter on that file name.		Then we can enter for e.g. function which we want to find, in which file it is? after entering function name, press enter.
			Cscope will list the names of files in which it has found that function. We can go through that file by pressing enter on that file name.
	Hyphenation Session by Shravan:		Hyphenation Session by Shravan:
	Hyphenation dictionary has all the rules.		Hyphenation dictionary has all the rules.

Missing actor at 12:22, 15 January 2011

2011-01-15T12:22:10Z

← Older revision		Revision as of 17:52, 15 January 2011
Line 14:		Line 14:
	power of distributed development.		power of distributed development.

	Linux kernel is maintained with git.		There are two types of Version Control Systems.
			Centralized Version Control System. e.g. CVS
			Distributed Version Control System. e.g. git, bazzar

			Linux kernel is maintained with git. Git is Distributed Version Control System.

			In distributed version control system, we can work remote place by just cloning the code from server. We do not depend on the server every time. That is any one in the world can contribute to your code, even if there is no Internet connection (except at time of cloning and submission). This is principal of FOSS development. Git is designed to be fast for merging codes from developer's.

			In centralized version control system, we need to have Internet connection every time, when you want contribute. This is main disadvantage of it.

	What do we want from git?		What do we want from git?
Line 41:		Line 49:

	Bug-tracking system: on every project website.		Bug-tracking system: on every project website.


	Code Browsing tips by Abhijit Sir:		Code Browsing tips by Abhijit Sir:
Line 53:		Line 62:
	* Keep writing notes and draw diagrams of data structures.		* Keep writing notes and draw diagrams of data structures.

			Code Browsing tools:
			*cscope
			*ctags
			*doxygen

			After installing cscope and ctags. Go to directory in which source code is.
			$ctags .c .h
			Then actual code browsing can be done using cscope.
			$scope
			Then we can enter for e.g. function which we want to find, in which file it is? after entering function name, press enter. Cscope will list the names of files in which it has found that function. We can go through that file by pressing enter on that file name.
	Hyphenation Session by Shravan:		Hyphenation Session by Shravan:
	Hyphenation dictionary has all the rules.		Hyphenation dictionary has all the rules.

Pravs: kdes git plans linked

2011-01-13T09:48:24Z

kdes git plans linked

← Older revision		Revision as of 15:18, 13 January 2011
Line 76:		Line 76:

	* [http://live.gnome.org/DistributedSCM GNOME projects evaluation of distributed source code management systems for migration from svn]		* [http://live.gnome.org/DistributedSCM GNOME projects evaluation of distributed source code management systems for migration from svn]
			* [http://techbase.kde.org/Projects/MovetoGit KDE project's plan to move to git]

Pravs: added references

2011-01-13T09:46:07Z

added references

← Older revision		Revision as of 15:16, 13 January 2011
Line 72:		Line 72:

	Thursday 1730 Revolution OS Film Screening; Seminar Hall.		Thursday 1730 Revolution OS Film Screening; Seminar Hall.

			== References ==

			* [http://live.gnome.org/DistributedSCM GNOME projects evaluation of distributed source code management systems for migration from svn]

Missing actor at 07:04, 9 January 2011

2011-01-09T07:04:41Z

← Older revision		Revision as of 12:34, 9 January 2011
Line 43:		Line 43:

	Code Browsing tips by Abhijit Sir:		Code Browsing tips by Abhijit Sir:
	1. READIT (Go through the README file).		* READIT (Go through the README file).
	2. Use tools like cscope and ctags.		* Use tools like cscope and ctags.
	3. Read and understand the data structure.		* Read and understand the data structure.
	4. Find the mainline.		* Find the mainline.
	5. 30-50% is error checking code. Ignore it for initial study.		* 30-50% is error checking code. Ignore it for initial study.
	6. Many header files in large C code, often nested.		* Many header files in large C code, often nested.
	7. C is being used in object oriented programming, with functions pointers heavily used.		* C is being used in object oriented programming, with functions pointers heavily used.
	8. What you cant find with an automated tool, might be in a library. Try to avoid reading those internals. Go for library documentation. Or it may be in a different language.		* What you cant find with an automated tool, might be in a library. Try to avoid reading those internals. Go for library documentation. Or it may be in a different language.
	9. Keep writing notes and draw diagrams of data structures.		* Keep writing notes and draw diagrams of data structures.

	Hyphenation Session by Shravan:		Hyphenation Session by Shravan:

Missing actor at 06:57, 9 January 2011

2011-01-09T06:57:53Z

← Older revision		Revision as of 12:27, 9 January 2011
Line 50:		Line 50:
	6. Many header files in large C code, often nested.		6. Many header files in large C code, often nested.
	7. C is being used in object oriented programming, with functions pointers heavily used.		7. C is being used in object oriented programming, with functions pointers heavily used.
	8. What you cant find with an automated tool, might be in a library.		8. What you cant find with an automated tool, might be in a library. Try to avoid reading those internals. Go for library documentation. Or it may be in a different language.
	Try to avoid reading those internals. Go for library documentation.
	Or it may be in a different language.
	9. Keep writing notes and draw diagrams of data structures.		9. Keep writing notes and draw diagrams of data structures.

Missing actor: Created page with "FOSS Lecture: (notes taken on the fly by Nishchay Mhatre; nishchaymhatre@gmail.com) Sat Jan 8 09:54:14 IST 2011 ---- Version Control session by Abhijit Sir: gcc 4.4.3 first..."

2011-01-09T06:57:23Z

Created page with "FOSS Lecture: (notes taken on the fly by Nishchay Mhatre; nishchaymhatre@gmail.com) Sat Jan 8 09:54:14 IST 2011 ---- Version Control session by Abhijit Sir: gcc 4.4.3 first..."

New page

FOSS Lecture: (notes taken on the fly by Nishchay Mhatre; nishchaymhatre@gmail.com)

Sat Jan 8 09:54:14 IST 2011

----

Version Control session by Abhijit Sir:

gcc 4.4.3
first 4 is major number
second 4 is minor number

'Dated directory' system: Wasteful,manual,time consuming, hard to document, cannot leverage the
power of distributed development.

Linux kernel is maintained with git.

What do we want from git?
- Naming of versions
- Save the state of the development : remember the changes
- Let us use an older version
- Ease of porting changes

Mainline of development is the 'Trunk' or master.
Branching is more for bug fixing.

Git can merge from different sources.

What security measures and administration in git?

Commit-Pull problem: After pull, the log is not showing the change but the file is getting
added without the add file command being used.

In git you cannot recover an older version unless it is branched out. If the reversion is done
on the trunk, the new stuff is lost. No version numbers in git.

Upstream/downstream concept: A developer who fixes a bug in a software obtained from the community
has to send the bug 'upstream' to the maintainers of the project.
The original maintainers of the code can fix the bug and send it 'downstream' to those who
have obtained the code from them.

Bug-tracking system: on every project website.

Code Browsing tips by Abhijit Sir:
1. READIT (Go through the README file).
2. Use tools like cscope and ctags.
3. Read and understand the data structure.
4. Find the mainline.
5. 30-50% is error checking code. Ignore it for initial study.
6. Many header files in large C code, often nested.
7. C is being used in object oriented programming, with functions pointers heavily used.
8. What you cant find with an automated tool, might be in a library.
Try to avoid reading those internals. Go for library documentation.
Or it may be in a different language.
9. Keep writing notes and draw diagrams of data structures.

Hyphenation Session by Shravan:
Hyphenation dictionary has all the rules.
To install it, the file has to be properly named and then added to the open
office repository.

----

~~Homework for the week~~
* Compile gnash
* Compile kde svn trunk version on gnome.
* Compile gnome (long term)
* Signup on foss community wiki and update user page
* Create makefile for hyphenation
* Setup your own debian-testing virtualbox image. On PD
* How to report a bug?
* Start on Debian new maintainters guide, see hyphenation wiki.

Thursday 1730 Revolution OS Film Screening; Seminar Hall.