Git - Revision history

Ralf: /* Which git protocol to use */ - document https

2012-08-20T18:14:04Z

‎Which git protocol to use: - document https

Ralf: Update repository URLs and a few other things.

2011-11-03T00:10:23Z

Update repository URLs and a few other things.

Ralf: Gitweb has moved.

2010-07-08T13:42:27Z

Gitweb has moved.

Alec v: /* See also */

2009-02-13T14:31:30Z

‎See also

Horsten: Fixup git url's to use git.linux-mips.org consistently

2008-02-27T11:57:57Z

Fixup git url's to use git.linux-mips.org consistently

Alex at 15:52, 4 December 2007

2007-12-04T15:52:51Z

Ralf: Update disk speed needs for Linux 2.6.21.

2007-04-26T09:17:01Z

Update disk speed needs for Linux 2.6.21.

Ctaylor: /* See also */

2007-03-27T22:23:17Z

‎See also

Abosaleem: /* See also */

2007-03-07T19:35:48Z

‎See also

Ralf: The Linux/MIPS repository on kernel.org.

2007-01-24T16:27:01Z

The Linux/MIPS repository on kernel.org.

@@ Line 50: / Line 50: @@
 * git Git's own protocol which tries to heavily optimize the amount of bandwidth used and thus is generally very efficient for updates.  An issue with the git protocol is its use of TCP port 9418 which [[Wikipedia:Paranoia|paranoid]] firewall admins may have blocked.
 * http Rather inefficient usage of bandwith and CPU but since http is generally enabled in firewalls it exists for those poor souls suffering from [[Wikipedia:Fascist|fascist]] firewall admins.
 * rsync The oldest git protocol, deprecated and supposed to eventually go away.  Suffers from a low probability race condition.  Its advantage is the lowest CPU usage on the server side.  Also some firewalls that don't allow git git protocol will allow rsync.  Not recommended for pulling or fetching.  Heck, it really should be considered the last alternative.  Rsync is not what in git parlance is called an intelligent transport which means that all new pack files on the server side will be transfered to the client even if only a single object from the pack would need to be transfered.  This however also means the bandwidth consumption can be excessive and is why rsync is no longer available as a git transport on linux-mips.org.

@@ Line 18: / Line 18: @@
 === Cloning a repository ===
-     git clone git://git.linux-mips.org/pub/scm/linux
+     git clone git://git.linux-mips.org/pub/scm/ralf/linux
 This will create a new directory under the current working directory called linux.
@@ Line 24: / Line 24: @@
 Here is an alternate form of the command which creates a local directory called linux.git instead of linux.
-     git clone git://git.linux-mips.org/pub/scm/linux linux.git
+     git clone git://git.linux-mips.org/pub/scm/ralf/linux linux.git
 === Updating a repository ===
@@ Line 39: / Line 39: @@
 It is also possible to specify an alternate URL by specifying it on the command line.
-     git pull git://git.linux-mips.org/pub/scm/linux
+     git pull git://git.linux-mips.org/pub/scm/ralf/linux
 Typing in URLs can be tedious.  You may create shortcuts to repeatedly used URLs by saving them in a remotes file.
 Alternate URLs may be saved in the <tt>.git/remotes/REMOTENAME</tt> file where the <tt>REMOTENAME</tt> string is the name that you wish to call that source location.  Let's say that that you wanted to clone this long URL
-<tt>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git</tt> but find that a lot to type repeatedly.
+<tt>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git</tt> but find that a lot to type repeatedly.
 If that is specified in a remotes file <tt>linus</tt> then the following command would pull from it.  <tt>git pull linus</tt>
@@ Line 50: / Line 50: @@
 * git Git's own protocol which tries to heavily optimize the amount of bandwidth used and thus is generally very efficient for updates.  An issue with the git protocol is its use of TCP port 9418 which [[Wikipedia:Paranoia|paranoid]] firewall admins may have blocked.
 * http Rather inefficient usage of bandwith and CPU but since http is generally enabled in firewalls it exists for those poor souls suffering from [[Wikipedia:Fascist|fascist]] firewall admins.
-* rsync The oldest git protocol, deprecated and supposed to eventually go away.  Suffers from a low probability race condition.  Its advantage is the lowest CPU usage on the server side.  Not recommended for pulling or fetching.  Heck, it really should be considered the last alternative.
+* rsync The oldest git protocol, deprecated and supposed to eventually go away.  Suffers from a low probability race condition.  Its advantage is the lowest CPU usage on the server side.  Also some firewalls that don't allow git git protocol will allow rsync.  Not recommended for pulling or fetching.  Heck, it really should be considered the last alternative.  Rsync is not what in git parlance is called an intelligent transport which means that all new pack files on the server side will be transfered to the client even if only a single object from the pack would need to be transfered.  This however also means the bandwidth consumption can be excessive and is why rsync is no longer available as a git transport on linux-mips.org.
 == Status of CVS to GIT conversion ==
-At this time linux.git and linux-malta.git trees are in active use. [[arcboot|Arcboot]] is still being maintained in CVS; all other archives are only historical.
+All development has been moved to git.
 == A note on branches in the kernel repository linux.git ==
@@ Line 60: / Line 60: @@
 === The queue ===
-This repository at git://git.linux-mips.org/pub/scm/linux-queue.git contains all the patches which are queued up to be sent to Linus but currently are not being sent because we're currently in the stabilization phase for an upcoming release.  The repository is frequently being [[git:git-rebase|rebased]] to avoid piling up history and doing lots of merges which later on will just make the history unreadable.  Also patches may be updated, replaced or dropped.  It therefor is not recommendable to create your own branch based on this repository's queue branch&nbsp;- or at least you should not do unless you ''know'' what you're doing.  Of course as long as you're not updating your repository by pulling again from the queue branch you're also safe but if you want to fetch this queue branch anyway you want to use the "+" modifier before your refspec.  See the <tt>git-fetch</tt> or <tt>git-pull</tt> man pages for what this exactly means.
+This repository at git://git.linux-mips.org/pub/scm/ralf/linux-queue.git contains all the patches which are queued up to be sent to Linus but currently are not being sent because we're currently in the stabilization phase for an upcoming release.  The repository is frequently being [[git:git-rebase|rebased]] to avoid piling up history and doing lots of merges which later on will just make the history unreadable.  Also patches may be updated, replaced or dropped.  It therefor is not recommendable to create your own branch based on this repository's queue branch&nbsp;- or at least you should not do unless you ''know'' what you're doing.  Of course as long as you're not updating your repository by pulling again from the queue branch you're also safe but if you want to fetch this queue branch anyway you want to use the "+" modifier before your refspec.  See the <tt>git-fetch</tt> or <tt>git-pull</tt> man pages for what this exactly means.
 So why does the queue repository with all these restrictions exist then I hear you ask?  It's meant to allow people to peek into what patches will go to Linus soon and to create patches that will apply cleanly.  It's also a place where patches can ripen before they make it into the main repository.
@@ Line 70: / Line 70: @@
 * git://git.kernel.org/pub/scm/linux/kernel/git/ralf/linux.git
-Note that while kernel.org has a massive total of 2 gigabit network bandwidth it is currently very overloaded and due two the staged server system on kernel.org the copy of the git tree there may lag anywhere between 15min to over a day behind its linux-mips.org equivalent.
+Note that while kernel.org has a massive total of 2 gigabit network bandwidth it is currently very overloaded and due to the staged server system on kernel.org the copy of the git tree there may lag anywhere between 15min to over a day behind its linux-mips.org equivalent.
 == The linux-malta.git repository ==
-The MaltaRef_2_6 branch on linux-malta.git used to be a stable, tested kernel recommended for the [[Mips Malta]].  It contains a superset of linux.git with the addition of two stable branches <tt>MaltaRef_2_6</tt> and <tt>MaltaRef_2_4</tt>.  This repository has been obsoleted.  All changes now go straight into the main Linux repository and unless you're seeking a Malta hardened older kernel version you're probably better off if you use the <tt>linux.git</tt> repository.
+The MaltaRef_2_6 branch on linux-malta.git used to be a stable, tested kernel recommended for the [[MIPS Malta]].  It contains a superset of linux.git with the addition of two stable branches <tt>MaltaRef_2_6</tt> and <tt>MaltaRef_2_4</tt>.  This repository has been obsoleted.  All changes now go straight into the main Linux repository and unless you're seeking a Malta hardened older kernel version you're probably better off if you use the <tt>linux.git</tt> repository.
 == Checking out a tagged release with git ==

@@ Line 117: / Line 117: @@
 == Gitweb ==
-Gitweb allows simple browsing of git repositories in a web browser.  Git web is available at http://www.linux-mips.org/git.
+Gitweb allows simple browsing of git repositories in a web browser.  Git web is available at http://git.linux-mips.org.
 == See also ==

@@ Line 120: / Line 120: @@
 == See also ==
 * [http://kernel.org/pub/software/scm/git/docs/tutorial.html A short git tutorial] at [http://www.kernel.org kernel.org]
 * [http://git.or.cz The GIT homepage]

@@ Line 14: / Line 14: @@
 == Accessing GIT repositories ==
-The GIT repositories can be accessed by <tt>git://ftp.linux-mips.org/pub/scm</tt>.   The http and rsync protocols are also supported but not recommended.  Here are two example commands using the <tt>linux.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>linux.git</tt> in the examples.
+The GIT repositories can be accessed by <tt>git://git.linux-mips.org/pub/scm</tt>.   The http and rsync protocols are also supported but not recommended.  Here are two example commands using the <tt>linux.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>linux.git</tt> in the examples.
 === Cloning a repository ===
-     git clone git://ftp.linux-mips.org/pub/scm/linux
+     git clone git://git.linux-mips.org/pub/scm/linux
 This will create a new directory under the current working directory called linux.
@@ Line 24: / Line 24: @@
 Here is an alternate form of the command which creates a local directory called linux.git instead of linux.
-     git clone git://ftp.linux-mips.org/pub/scm/linux linux.git
+     git clone git://git.linux-mips.org/pub/scm/linux linux.git
 === Updating a repository ===
@@ Line 39: / Line 39: @@
 It is also possible to specify an alternate URL by specifying it on the command line.
-     git pull git://ftp.linux-mips.org/pub/scm/linux
+     git pull git://git.linux-mips.org/pub/scm/linux
 Typing in URLs can be tedious.  You may create shortcuts to repeatedly used URLs by saving them in a remotes file.

← Older revision		Revision as of 15:52, 4 December 2007
Line 124:		Line 124:
	* [[Mailing-patches]] How to email patches for submission into the kernel.		* [[Mailing-patches]] How to email patches for submission into the kernel.
	* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.		* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.
		+
		+
		+	[[Category:git]]

@@ Line 112: / Line 112: @@
 == Disk space requirements for the kernel repository ==
-As of this writing the size is approximately 63MB compared to 312MB for the full repository and the size saving of the shallow repository - obviously - comes at the price of the history before 2.6.15.    Other than that the tree is identical to the main git kernel repository.  Additional 275MB are needed for checking out the repository plus another upto 85MB for building - even more for very large configurations, debugging etc.
+As of <tt>linux-2.6.21</tt> the size is 308MB for the full repository.  Users of git&nbsp;1.5.0 and newer can use a git feature named ''shallow tree'' to prune the history.  This can reduce the repository to as little as 112MB.  An additional 297MB are needed for checking out the repository plus another upto 90MB for building - even more for very large configurations, debugging etc.
-Using ''aggressive'' compression settings (see [[git:git-pack-objects|git-pack-objects]] manpage) on the order of 70MB can be saved for the full repository at the price of somewhat lower performance.  Linux-mips.org stopped doing so as it puts an inacceptable burden on the aging server machine.
+Using ''aggressive'' compression settings (see [[git:git-pack-objects|git-pack-objects]] manpage) on the order of 70MB can be saved for the full repository at the price of somewhat lower performance.
 == Gitweb ==

← Older revision		Revision as of 22:23, 27 March 2007
Line 124:		Line 124:
	* [[Mailing-patches]] How to email patches for submission into the kernel.		* [[Mailing-patches]] How to email patches for submission into the kernel.
	* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.		* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.
−	* [http://www.alragib.com/vb/ Ø¨ÙŠØª]
−	* [http://www.alragib.com/fateh/ ÙØªØ]

← Older revision		Revision as of 19:35, 7 March 2007
Line 124:		Line 124:
	* [[Mailing-patches]] How to email patches for submission into the kernel.		* [[Mailing-patches]] How to email patches for submission into the kernel.
	* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.		* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.
		+	* [http://www.alragib.com/vb/ Ø¨ÙŠØª]
		+	* [http://www.alragib.com/fateh/ ÙØªØ]

← Older revision		Revision as of 16:27, 24 January 2007
Line 63:		Line 63:

	So why does the queue repository with all these restrictions exist then I hear you ask? It's meant to allow people to peek into what patches will go to Linus soon and to create patches that will apply cleanly. It's also a place where patches can ripen before they make it into the main repository.		So why does the queue repository with all these restrictions exist then I hear you ask? It's meant to allow people to peek into what patches will go to Linus soon and to create patches that will apply cleanly. It's also a place where patches can ripen before they make it into the main repository.
		+
		+	=== Linux/MIPS on kernel.org ===
		+	A copy of the Linux/MIPS kernel repository is also maintained on kernel.org. It is accessible at:
		+
		+	* http://www.kernel.org/git/?p=linux/kernel/git/ralf/linux.git;a=summary (gitweb)
		+	* git://git.kernel.org/pub/scm/linux/kernel/git/ralf/linux.git
		+
		+	Note that while kernel.org has a massive total of 2 gigabit network bandwidth it is currently very overloaded and due two the staged server system on kernel.org the copy of the git tree there may lag anywhere between 15min to over a day behind its linux-mips.org equivalent.

	== The linux-malta.git repository ==		== The linux-malta.git repository ==