GIT - Revision history

DL9SAU at 10:10, 16 September 2022

2022-09-16T10:10:58Z

← Older revision		Revision as of 10:10, 16 September 2022
Line 24:		Line 24:

	git clone git://linux-ax25.in-berlin.de/pub/scm/libax25 linux.git		git clone git://linux-ax25.in-berlin.de/pub/scm/libax25 linux.git
	[git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git]		[old: git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git]

	=== Updating a repository ===		=== Updating a repository ===
Line 61:		Line 61:

	git pull git://linux-ax25.in-berlin.de/pub/scm/libax25		git pull git://linux-ax25.in-berlin.de/pub/scm/libax25
	[git pull git://git.linux-ax25.org/pub/scm/libax25]		[old: git pull git://git.linux-ax25.org/pub/scm/libax25]

	Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.		Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.

DL9SAU at 10:10, 16 September 2022

2022-09-16T10:10:28Z

← Older revision		Revision as of 10:10, 16 September 2022
Line 24:		Line 24:

	git clone git://linux-ax25.in-berlin.de/pub/scm/libax25 linux.git		git clone git://linux-ax25.in-berlin.de/pub/scm/libax25 linux.git
	git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git		[git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git]

	=== Updating a repository ===		=== Updating a repository ===

DL9SAU at 10:08, 16 September 2022

2022-09-16T10:08:41Z

← Older revision		Revision as of 10:08, 16 September 2022
Line 37:		Line 37:

	This will pull updates from the repository and merge them into your local repository.		This will pull updates from the repository and merge them into your local repository.


			How to actually compile is documented in [[Compilation]].

DL9SAU at 09:53, 16 September 2022

2022-09-16T09:53:47Z

← Older revision		Revision as of 09:53, 16 September 2022
Line 12:		Line 12:

	== Accessing GIT repositories ==		== Accessing GIT repositories ==
	The GIT repositories can be accessed by <tt>git://~~git.~~linux-ax25.~~org~~/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.		The GIT repositories can be accessed by <tt>git://linux-ax25.in-berlin.de/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.

	=== Cloning a repository ===		=== Cloning a repository ===
Line 57:		Line 57:
	It is also possible to specify an alternate URL by specifying it on the command line.		It is also possible to specify an alternate URL by specifying it on the command line.

	git pull git://~~git.~~linux-ax25.~~org~~/pub/scm/libax25		git pull git://linux-ax25.in-berlin.de/pub/scm/libax25
	[git pull git://git.linux-ax25.org/pub/scm/libax25]		[git pull git://git.linux-ax25.org/pub/scm/libax25]

Line 69:		Line 69:
	* 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.		* 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.		* 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.
	* https More secure than http but otherwise pretty much the same thing. linux-ax25.~~org uses SSL certificates from cacert~~.~~org and CACERT's root certificate is not included with most operating systems. A notable exception is Debian however. So if attempts to access a~~ linux-ax25.org repository via https fail with an error message about an invalid SSL certificate, you can:		* https More secure than http but otherwise pretty much the same thing. If attempts to access a linux-ax25.in-berlin.de (exx: linux-ax25.org) repository via https fail with an error message about an invalid SSL certificate, you can:
	** use one of the other protocols listed in this section		** use one of the other protocols listed in this section
	** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://~~git.~~linux-ax25.~~org~~/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.		** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://linux-ax25.in-berlin.de/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.
	** manually import the root certificate. The preferable but also most complicated approach.		** manually import the root certificate. The preferable but also most complicated approach.
	* 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.		* 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.
Line 104:		Line 104:

	== Gitweb ==		== Gitweb ==
	Gitweb allows simple browsing of git repositories in a web browser. Git web is available at ~~http~~://~~git.~~linux-ax25.~~org~~.		Gitweb allows simple browsing of git repositories in a web browser. Git web is available at https://linux-ax25.in-berlin.de/git/.

	== See also ==		== See also ==

DL9SAU at 09:49, 16 September 2022

2022-09-16T09:49:39Z

← Older revision		Revision as of 09:49, 16 September 2022
Line 16:		Line 16:
	=== Cloning a repository ===		=== Cloning a repository ===

	git clone git://git.linux-ax25.org/pub/scm/libax25		git clone git://linux-ax25.in-berlin.de/pub/scm/libax25
			[old: git clone git://git.linux-ax25.org/pub/scm/libax25]

	This will create a new directory under the current working directory called linux.		This will create a new directory under the current working directory called linux.
Line 22:		Line 23:
	Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.		Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.

			git clone git://linux-ax25.in-berlin.de/pub/scm/libax25 linux.git
	git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git		git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git

	=== Updating a repository ===		=== Updating a repository ===

	When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.		When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.
	This is the default location for git to pull updates.		This is the default location for git to pull updates.
Line 34:		Line 37:

	This will pull updates from the repository and merge them into your local repository.		This will pull updates from the repository and merge them into your local repository.



			Since of summer 2022 we have a problem with our domain linux-ax25.org.
			If you already cloned to a local repository, please update the URL for your repo:

			$ for repo in libax25 ax25-apps ax25-tools; do
			if [ -d $repo ]; then
			cd $repo
			git remote set-url origin git://linux-ax25.in-berlin.de/pub/scm/$repo
			cd ..
			else
			echo "local $repo does not exist"
			fi
			done



	It is also possible to specify an alternate URL by specifying it on the command line.		It is also possible to specify an alternate URL by specifying it on the command line.

	git pull git://git.linux-ax25.org/pub/scm/libax25		git pull git://git.linux-ax25.org/pub/scm/libax25
			[git pull git://git.linux-ax25.org/pub/scm/libax25]

	Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.		Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.

DL5RB: /* See also */ Fix stale URLs, switch to protocol agnostic URLs

2016-11-24T19:05:10Z

See also: Fix stale URLs, switch to protocol agnostic URLs

← Older revision		Revision as of 19:05, 24 November 2016
Line 87:		Line 87:
	== See also ==		== See also ==
	* [[Compilation]] How to build <tt>libax25</tt>, <tt>ax25-tools</tt> or <tt>ax25-apps</tt> from source.		* [[Compilation]] How to build <tt>libax25</tt>, <tt>ax25-tools</tt> or <tt>ax25-apps</tt> from source.
	* [~~http:~~//kernel.org/pub/software/scm/git/docs/~~tutorial~~.html A short git tutorial] at [~~http:~~//www.kernel.org kernel.org]		* [//kernel.org/pub/software/scm/git/docs/gittutorial.html A short git tutorial] at [//www.kernel.org kernel.org]
	* [~~http:~~//git.~~or.cz~~ The GIT homepage]		* [//git-scm.com The GIT homepage]
	* ~~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.		* [//www.ibm.com/developerworks/library/l-vercon/ A nice SCM article] by IBM giving an overview what SCM is and several popular SCM systems.


	[[Category:git]]		[[Category:git]]

DL5RB: /* Status of CVS to GIT conversion */

2015-04-26T18:19:09Z

Status of CVS to GIT conversion

← Older revision		Revision as of 18:19, 26 April 2015
Line 56:		Line 56:
	== Status of CVS to GIT conversion ==		== Status of CVS to GIT conversion ==

	All development has been moved to git. It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.		All development has been moved to git. For the time being the CVS Server is still running to maintain the history and help users with existing CVS checkouts however there will be ''no'' more CVS checkins.

			It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.

	== Checking out a tagged release with git ==		== Checking out a tagged release with git ==

DL5RB: Link to compilation notes page.

2013-06-04T14:50:30Z

Link to compilation notes page.

← Older revision		Revision as of 14:50, 4 June 2013
Line 84:		Line 84:

	== See also ==		== See also ==
			* [[Compilation]] How to build <tt>libax25</tt>, <tt>ax25-tools</tt> or <tt>ax25-apps</tt> from source.
	* [http://kernel.org/pub/software/scm/git/docs/tutorial.html A short git tutorial] at [http://www.kernel.org kernel.org]		* [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]		* [http://git.or.cz The GIT homepage]
	* 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]]		[[Category:git]]

DL5RB: A git primer for linux-ax25.org users.

2013-06-04T14:38:54Z

A git primer for linux-ax25.org users.

New page

<h4 style="background-color:#efefff;border-bottom: 0px;border: 1px solid #1e90ff;text-align:left;padding-top:4px;margin-top:5px; ">
::We will hereby start scouring the net for people who say git is hard to
::understand and use, and just kill them. They clearly are just polluting
::the gene pool.
:
::::Linus
</h4>
<div style="padding-left:2em;padding-right:2em;">

All right, we're not quite that bad. Yet. These days the Linux world has largely switched to '''GIT''' as its SCM. Git is a fairly low-level thing, more the backing store of an SCM - or ''plumbing'' in Linus's words - than a full-blown SCM but it's growing up very quickly. Linux-ax25.org has used [[CVS]] since [[2001]] and so naturally is a little more conservative in switching to a new tools as we don't want to drop all the history that's hidden in these trees.

== Accessing GIT repositories ==
The GIT repositories can be accessed by <tt>git://git.linux-ax25.org/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.

=== Cloning a repository ===

git clone git://git.linux-ax25.org/pub/scm/libax25

This will create a new directory under the current working directory called linux.
To use a different name specify it on the command line as an additional argument and it will become the target.
Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.

git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git

=== Updating a repository ===
When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.
This is the default location for git to pull updates.
If you wish to modify the default URL you may edit that file directly.

From the top directory of your local repository (that is, the directory which contains the <tt>.git</tt> subdirectory) run the following command:

git pull

This will pull updates from the repository and merge them into your local repository.

It is also possible to specify an alternate URL by specifying it on the command line.

git pull git://git.linux-ax25.org/pub/scm/libax25

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.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>

=== Which git protocol to use ===
Generally these days the git protocol (the <tt>git://</tt>) URLs) is the prefered protocol.
* 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.
* https More secure than http but otherwise pretty much the same thing. linux-ax25.org uses SSL certificates from cacert.org and CACERT's root certificate is not included with most operating systems. A notable exception is Debian however. So if attempts to access a linux-ax25.org repository via https fail with an error message about an invalid SSL certificate, you can:
** use one of the other protocols listed in this section
** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://git.linux-ax25.org/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.
** manually import the root certificate. The preferable but also most complicated approach.
* 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.

== Status of CVS to GIT conversion ==

All development has been moved to git. It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.

== Checking out a tagged release with git ==
This is how to list the available tags:

<pre>
[ralf@dea linux-git]$ git tag -l
$ git tag -l
libax25-0.0.10
libax25-0.0.11
libax25-0.0.12-rc1
libax25-0.0.12-rc2
libax25-0.0.12-rc3
...
</pre>

The actual list of tags is longer. Okay, so let's assume we want to checkout the <tt>libax25-0.0.11</tt> release:

<pre>
[ralf@dea linux-git]$ git checkout -b my-0.0.11 libax25-0.0.11
</pre>

What this exactly does is creating a ''new'' branch named <tt>my-0.0.11</tt> at <tt>linux-0.0.11</tt> and checking out it's HEAD.

== Gitweb ==
Gitweb allows simple browsing of git repositories in a web browser. Git web is available at http://git.linux-ax25.org.

== 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]
* 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]]