The document is a user manual for Git Extensions, which is a toolkit that aims to make working with Git under Windows more intuitive. It provides features like Windows Explorer integration for Git, a Visual Studio plug-in for Git, and a feature-rich user interface. The manual covers topics like installation, settings, cloning repositories, committing changes, branches, remotes, and integration with Visual Studio and Windows Explorer. It also includes links to video tutorials on basic Git Extensions functions.
This document provides an overview of a Linux system administration training course. It covers 28 chapters on topics like the Unix command line, file management, processes, filesystems, backups and more. Each chapter includes detailed explanations, examples and exercises to help system administrators effectively manage and maintain Linux systems.
This document provides instructions for administering IPCop v1.4.21, an open-source firewall/router operating system. It discusses the administrative web interface for configuring system updates, passwords, SSH access, backups and shutdown. It also describes how to view system status information like services, memory/disk usage, networks status and traffic graphs. The document outlines how to configure network services like the web proxy, DHCP server, and external network aliases.
Red Hat Enterprise Linux 4 System Administration Guide provides documentation on installation, configuration, and administration of Red Hat Enterprise Linux 4 systems. Key topics covered include kickstart installations, Logical Volume Manager (LVM), Software RAID, package management, network configuration, firewall configuration, NFS, Samba, DHCP, Apache, authentication, console access, users/groups, printers, and more. The guide is intended to help system administrators manage and maintain Red Hat Enterprise Linux servers.
The document provides documentation for installing Fedora 17 on x86, AMD64 and Intel 64 systems. It includes instructions for downloading and preparing installation media, planning hardware requirements, starting the installation process, completing installation using the graphical or text-based interface, and troubleshooting installation issues. The guide also covers advanced installation options such as disk partitioning, encrypted partitions, Kickstart automation and setting up a network installation server.
This document provides instructions for configuring and managing Red Hat Cluster for Red Hat Enterprise Linux 5. It discusses setting up hardware and installing the Red Hat Cluster software. It then describes using the Conga and system-config-cluster tools to configure clusters, including defining global properties, cluster members, failover domains, resources, and services. It also covers starting, stopping, and managing clusters and troubleshooting problems.
This module prints a simple "Hello world 1" message when loaded and "Goodbye world 1" when unloaded. It implements the basic init_module and cleanup_module functions required for all kernel modules, which are called when the module is loaded and unloaded respectively. The module demonstrates the simplest form of a kernel module and introduces the printk function for printing from a module.
This document provides instructions for installing and administering R on various operating systems. It covers obtaining R sources, installing on Unix-like systems, Windows, and OS X. It also discusses installing add-on packages, internationalization, choosing 32- vs 64-bit builds, and using the standalone Rmath library. The document is intended as a manual for installing and managing R versions 3.0.2 or higher.
This document provides instructions for installing and administering R, the open-source statistical software and programming language. It covers obtaining R sources, installing on Unix-like and Windows systems, installing add-on packages, internationalization, and other topics. Permission is granted to distribute verbatim or modified copies of the manual under certain conditions.
This document provides an overview of a Linux system administration training course. It covers 28 chapters on topics like the Unix command line, file management, processes, filesystems, backups and more. Each chapter includes detailed explanations, examples and exercises to help system administrators effectively manage and maintain Linux systems.
This document provides instructions for administering IPCop v1.4.21, an open-source firewall/router operating system. It discusses the administrative web interface for configuring system updates, passwords, SSH access, backups and shutdown. It also describes how to view system status information like services, memory/disk usage, networks status and traffic graphs. The document outlines how to configure network services like the web proxy, DHCP server, and external network aliases.
Red Hat Enterprise Linux 4 System Administration Guide provides documentation on installation, configuration, and administration of Red Hat Enterprise Linux 4 systems. Key topics covered include kickstart installations, Logical Volume Manager (LVM), Software RAID, package management, network configuration, firewall configuration, NFS, Samba, DHCP, Apache, authentication, console access, users/groups, printers, and more. The guide is intended to help system administrators manage and maintain Red Hat Enterprise Linux servers.
The document provides documentation for installing Fedora 17 on x86, AMD64 and Intel 64 systems. It includes instructions for downloading and preparing installation media, planning hardware requirements, starting the installation process, completing installation using the graphical or text-based interface, and troubleshooting installation issues. The guide also covers advanced installation options such as disk partitioning, encrypted partitions, Kickstart automation and setting up a network installation server.
This document provides instructions for configuring and managing Red Hat Cluster for Red Hat Enterprise Linux 5. It discusses setting up hardware and installing the Red Hat Cluster software. It then describes using the Conga and system-config-cluster tools to configure clusters, including defining global properties, cluster members, failover domains, resources, and services. It also covers starting, stopping, and managing clusters and troubleshooting problems.
This module prints a simple "Hello world 1" message when loaded and "Goodbye world 1" when unloaded. It implements the basic init_module and cleanup_module functions required for all kernel modules, which are called when the module is loaded and unloaded respectively. The module demonstrates the simplest form of a kernel module and introduces the printk function for printing from a module.
This document provides instructions for installing and administering R on various operating systems. It covers obtaining R sources, installing on Unix-like systems, Windows, and OS X. It also discusses installing add-on packages, internationalization, choosing 32- vs 64-bit builds, and using the standalone Rmath library. The document is intended as a manual for installing and managing R versions 3.0.2 or higher.
This document provides instructions for installing and administering R, the open-source statistical software and programming language. It covers obtaining R sources, installing on Unix-like and Windows systems, installing add-on packages, internationalization, and other topics. Permission is granted to distribute verbatim or modified copies of the manual under certain conditions.
This document provides instructions for installing and administering R on various operating systems. It covers obtaining R sources, compiling and installing R under Unix-like systems, Windows, and Mac OS X. It also discusses running R, installing add-on packages, internationalization, choosing 32- vs 64-bit builds, and the standalone Rmath library.
This document provides an overview of using IBM Tivoli Configuration Manager to deploy Rational products. It describes the key components and services of Tivoli Configuration Manager that are useful for deployment. It then provides step-by-step instructions for preparing Rational products, creating deployment packages, and deploying the packages to managed nodes using Tivoli Configuration Manager. The document is intended for IT professionals tasked with deploying Rational products in an enterprise environment.
This document provides a table of contents for a book on Visual C++ and MFC fundamentals. The table of contents lists 10 chapters that cover topics such as the Visual C++ environment, the MFC library, windows resources, messages and events, and the document/view architecture. It provides an outline of the sections in each chapter.
This document provides an overview and instructions for installing, configuring, securing and using Hudson, an open source continuous integration server. It covers downloading and installing Hudson on various operating systems like Ubuntu, Red Hat and OpenSUSE. It also describes configuring global settings, plugins, projects and jobs in Hudson as well as securing Hudson through authentication and authorization. The document is intended as a manual for getting started with and managing Hudson.
Red Hat Enterprise Linux 4: Introduction to System Administration is a documentation guide that covers:
1. The philosophy of system administration including automating tasks, documenting processes, communicating with users, understanding resources and security.
2. Resource monitoring on Linux systems using tools like free, top, vmstat and the Sysstat suite to monitor CPU, memory, storage and bandwidth usage.
3. Managing bandwidth and processing power on Linux including monitoring techniques in Red Hat Enterprise Linux and improving performance by addressing bottlenecks.
This document is the user's guide for Akeeba Backup, a site backup component for Joomla-powered websites. It covers both the free Akeeba Backup Core and the subscription-based Professional editions. The guide is divided into sections that explain how to install and update Akeeba Backup, configure backup profiles and settings, perform backups, manage backup files, and include or exclude specific files, databases, and directories from backups. It provides instructions on all the major functions and features of Akeeba Backup.
This book provides guidance on designing and building embedded Linux systems. It introduces the topic and covers important concepts like hardware support, development tools, the Linux kernel, and root filesystem setup. The book explains how to configure, cross-compile, and install the kernel. It also describes manipulating storage devices and setting up the bootloader, networking services, and debugging tools. The goal is to help experienced embedded developers customize and use Linux in their projects without relying on third-party products.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
The document provides instructions for installing MongoDB on Red Hat Enterprise Linux, CentOS Linux, and Fedora Linux systems using RPM packages. It describes downloading and configuring the MongoDB YUM repository, then installing the mongo-10gen and mongo-10gen-server packages to get the latest stable version of MongoDB. It also discusses how to install a specific version and prevent unintended upgrades using YUM version pinning.
Red hat enterprise_linux-7-beta-installation_guide-en-usmuhammad adeel
This document provides an installation guide for Red Hat Enterprise Linux 7. It describes how to install RHEL 7 on AMD64, Intel 64, IBM Power Systems, and IBM System z architectures. The guide covers preparing installation media, planning hardware requirements, performing the installation, and troubleshooting installation issues. It also discusses advanced installation methods like Kickstart, PXE, and VNC installations.
hp StorageWorks host bus adapter for Windows and Linux ...webhostingguy
This document provides installation and configuration instructions for an HP StorageWorks host bus adapter (HBA) for Windows and Linux platforms. It describes how to install the HBA hardware, install device drivers for Windows Server 2003 and various Linux distributions, and use diagnostic utilities to test and configure the HBA. The guide covers hardware installation, driver installation, troubleshooting, and how to use utilities to diagnose and configure the HBA.
This document provides guidance on setting up IBM tape drives and libraries in multiple UNIX environments. It discusses IBM LTO Ultrium tape drive models, hardware platforms, connectivity options, partitioning of multi-path tape libraries, and SAN considerations for attaching tape libraries. The document is intended to help integrators and administrators implement IBM tape solutions for backup and archiving in UNIX environments.
The document provides an overview of getting started with GNU/Linux. It covers useful terminal shortcuts, file management commands like navigating directories, listing files, and copying/removing files. It also discusses detecting the Linux distribution, getting system information, and using common commands like ls, tar, ssh and more. The document is intended as a reference for Linux professionals.
This chapter discusses different types of software licenses:
- Proprietary licenses require payment of fees and do not allow access to source code. Examples include AIX, HP-UX, and Solaris 9.
- BSD licenses are open source and allow copying and modification with few restrictions other than retaining copyright notices.
- The GNU GPL is a prominent open source license that allows free use and modification of source code but requires any derived works to also be shared under the GPL.
- Other licenses discussed include free software, open source, freeware, and various other licenses with different terms.
MySQL Workbench is a visual tool for database design, creation, modeling, and administration. It allows users to design and create databases visually using EER diagrams or through a schema navigator. The tool also supports importing and exporting SQL scripts, creating tables and foreign key relationships, and documenting databases through generated diagrams and reports. MySQL Workbench is available in both open source and commercial editions.
The document provides step-by-step instructions for setting up an email server using Red Hat Linux 7. It discusses installing Red Hat Linux, configuring the network settings, installing and configuring DNS (BIND), sendmail, POP3, IMAP, and LDAP. The document contains details on installing necessary packages and configuring files to set up these various services and enable email functionality.
Tivoli Personalized Services Manager 1.1 supports pervasive devices, creates personalized service environments, and provides self care. It introduces new features including web hosting, a portal toolkit, Radius support, DB2 database support, localization, an improved device manager, and integration with IBM's WebSphere Everyplace suite. The document provides an overview of Tivoli Personalized Services Manager and its features for subscriber authentication, access control, customer care, personalized services, integration with third party tools, and support for emerging Internet business models.
TortoiseSVN is a Windows client for Subversion version control. It provides features for importing and exporting files to a repository, checking out working copies, committing changes, updating working copies, and viewing project history. The document discusses TortoiseSVN's installation, basic version control concepts, repository creation and management, daily use features like committing and updating, and resolving conflicts. It is intended as a user guide for getting started with and using TortoiseSVN for source control management.
This document provides information about login scripts in Novell, including:
- Where login scripts should be located and common login script commands
- Examples of sample login scripts for containers, profiles, users, and default scripts
- Descriptions of specific login script commands and variables like MAP, IF/THEN, and INCLUDE
Winserver 2012 R2 and Winserver 2012.TechnetEmilio
This document provides an overview of designing a private cloud infrastructure using Windows Server 2012 R2 and Windows Server 2012. It discusses key aspects of the cloud infrastructure including storage, networking, virtualization, and host design. Specific topics covered include storage options and protocols, cluster shared volumes, storage networking, network infrastructure design including traffic isolation, host licensing, memory configuration, and Hyper-V clustering.
This document provides instructions for installing and administering R on various operating systems. It covers obtaining R sources, compiling and installing R under Unix-like systems, Windows, and Mac OS X. It also discusses running R, installing add-on packages, internationalization, choosing 32- vs 64-bit builds, and the standalone Rmath library.
This document provides an overview of using IBM Tivoli Configuration Manager to deploy Rational products. It describes the key components and services of Tivoli Configuration Manager that are useful for deployment. It then provides step-by-step instructions for preparing Rational products, creating deployment packages, and deploying the packages to managed nodes using Tivoli Configuration Manager. The document is intended for IT professionals tasked with deploying Rational products in an enterprise environment.
This document provides a table of contents for a book on Visual C++ and MFC fundamentals. The table of contents lists 10 chapters that cover topics such as the Visual C++ environment, the MFC library, windows resources, messages and events, and the document/view architecture. It provides an outline of the sections in each chapter.
This document provides an overview and instructions for installing, configuring, securing and using Hudson, an open source continuous integration server. It covers downloading and installing Hudson on various operating systems like Ubuntu, Red Hat and OpenSUSE. It also describes configuring global settings, plugins, projects and jobs in Hudson as well as securing Hudson through authentication and authorization. The document is intended as a manual for getting started with and managing Hudson.
Red Hat Enterprise Linux 4: Introduction to System Administration is a documentation guide that covers:
1. The philosophy of system administration including automating tasks, documenting processes, communicating with users, understanding resources and security.
2. Resource monitoring on Linux systems using tools like free, top, vmstat and the Sysstat suite to monitor CPU, memory, storage and bandwidth usage.
3. Managing bandwidth and processing power on Linux including monitoring techniques in Red Hat Enterprise Linux and improving performance by addressing bottlenecks.
This document is the user's guide for Akeeba Backup, a site backup component for Joomla-powered websites. It covers both the free Akeeba Backup Core and the subscription-based Professional editions. The guide is divided into sections that explain how to install and update Akeeba Backup, configure backup profiles and settings, perform backups, manage backup files, and include or exclude specific files, databases, and directories from backups. It provides instructions on all the major functions and features of Akeeba Backup.
This book provides guidance on designing and building embedded Linux systems. It introduces the topic and covers important concepts like hardware support, development tools, the Linux kernel, and root filesystem setup. The book explains how to configure, cross-compile, and install the kernel. It also describes manipulating storage devices and setting up the bootloader, networking services, and debugging tools. The goal is to help experienced embedded developers customize and use Linux in their projects without relying on third-party products.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
The document provides instructions for installing MongoDB on Red Hat Enterprise Linux, CentOS Linux, and Fedora Linux systems using RPM packages. It describes downloading and configuring the MongoDB YUM repository, then installing the mongo-10gen and mongo-10gen-server packages to get the latest stable version of MongoDB. It also discusses how to install a specific version and prevent unintended upgrades using YUM version pinning.
Red hat enterprise_linux-7-beta-installation_guide-en-usmuhammad adeel
This document provides an installation guide for Red Hat Enterprise Linux 7. It describes how to install RHEL 7 on AMD64, Intel 64, IBM Power Systems, and IBM System z architectures. The guide covers preparing installation media, planning hardware requirements, performing the installation, and troubleshooting installation issues. It also discusses advanced installation methods like Kickstart, PXE, and VNC installations.
hp StorageWorks host bus adapter for Windows and Linux ...webhostingguy
This document provides installation and configuration instructions for an HP StorageWorks host bus adapter (HBA) for Windows and Linux platforms. It describes how to install the HBA hardware, install device drivers for Windows Server 2003 and various Linux distributions, and use diagnostic utilities to test and configure the HBA. The guide covers hardware installation, driver installation, troubleshooting, and how to use utilities to diagnose and configure the HBA.
This document provides guidance on setting up IBM tape drives and libraries in multiple UNIX environments. It discusses IBM LTO Ultrium tape drive models, hardware platforms, connectivity options, partitioning of multi-path tape libraries, and SAN considerations for attaching tape libraries. The document is intended to help integrators and administrators implement IBM tape solutions for backup and archiving in UNIX environments.
The document provides an overview of getting started with GNU/Linux. It covers useful terminal shortcuts, file management commands like navigating directories, listing files, and copying/removing files. It also discusses detecting the Linux distribution, getting system information, and using common commands like ls, tar, ssh and more. The document is intended as a reference for Linux professionals.
This chapter discusses different types of software licenses:
- Proprietary licenses require payment of fees and do not allow access to source code. Examples include AIX, HP-UX, and Solaris 9.
- BSD licenses are open source and allow copying and modification with few restrictions other than retaining copyright notices.
- The GNU GPL is a prominent open source license that allows free use and modification of source code but requires any derived works to also be shared under the GPL.
- Other licenses discussed include free software, open source, freeware, and various other licenses with different terms.
MySQL Workbench is a visual tool for database design, creation, modeling, and administration. It allows users to design and create databases visually using EER diagrams or through a schema navigator. The tool also supports importing and exporting SQL scripts, creating tables and foreign key relationships, and documenting databases through generated diagrams and reports. MySQL Workbench is available in both open source and commercial editions.
The document provides step-by-step instructions for setting up an email server using Red Hat Linux 7. It discusses installing Red Hat Linux, configuring the network settings, installing and configuring DNS (BIND), sendmail, POP3, IMAP, and LDAP. The document contains details on installing necessary packages and configuring files to set up these various services and enable email functionality.
Tivoli Personalized Services Manager 1.1 supports pervasive devices, creates personalized service environments, and provides self care. It introduces new features including web hosting, a portal toolkit, Radius support, DB2 database support, localization, an improved device manager, and integration with IBM's WebSphere Everyplace suite. The document provides an overview of Tivoli Personalized Services Manager and its features for subscriber authentication, access control, customer care, personalized services, integration with third party tools, and support for emerging Internet business models.
TortoiseSVN is a Windows client for Subversion version control. It provides features for importing and exporting files to a repository, checking out working copies, committing changes, updating working copies, and viewing project history. The document discusses TortoiseSVN's installation, basic version control concepts, repository creation and management, daily use features like committing and updating, and resolving conflicts. It is intended as a user guide for getting started with and using TortoiseSVN for source control management.
This document provides information about login scripts in Novell, including:
- Where login scripts should be located and common login script commands
- Examples of sample login scripts for containers, profiles, users, and default scripts
- Descriptions of specific login script commands and variables like MAP, IF/THEN, and INCLUDE
Winserver 2012 R2 and Winserver 2012.TechnetEmilio
This document provides an overview of designing a private cloud infrastructure using Windows Server 2012 R2 and Windows Server 2012. It discusses key aspects of the cloud infrastructure including storage, networking, virtualization, and host design. Specific topics covered include storage options and protocols, cluster shared volumes, storage networking, network infrastructure design including traffic isolation, host licensing, memory configuration, and Hyper-V clustering.
The document discusses mobile technologies and learning. It provides an update on mobile phone technology, including that mobile phones have surpassed PCs in numbers owned worldwide. It describes the m-learning project, which developed learning materials to run on mobile devices and conducted learner research and systems trials. Key findings from the trials indicated that mobile devices can successfully engage hard to reach learners and have potential to improve their skills and self-confidence when used as part of blended learning.
When he was little, William Phair enjoyed school, playing in the park, and watching TV shows like Tweenies, Teletubbies, and Bob the Builder. He disliked going to sleep and playing alone. His favorite toys included action figures, toy cars, and playing with his brother.
The telephone was invented by Alexander Graham Bell in 1876 to allow people separated by large distances to communicate by transmitting sound, most commonly the human voice. Bell received the first patent for the telephone on March 7, 1876 while living in Salem, Massachusetts, creating the first device that could transmit sound over wires to connect people in different locations.
The document is a guide for obtaining certification in IBM Tivoli Provisioning Manager V5.1. It discusses the IBM Professional Certification Program and the benefits of certification. It also provides details on the certification path and prerequisites for the Tivoli Provisioning Manager V5.1 Implementation certification, including recommended study resources such as courses and publications. The guide helps readers learn about and prepare for the certification test for Tivoli Provisioning Manager V5.1.
Magento Extension - Google Custom Search by Solwin InfotechSolwin Infotech
This document provides a user guide for the Google Custom Search Integration Magento extension. The extension allows merchants to integrate Google's Custom Search Engine into their Magento store to enhance search functionality and improve SEO by returning custom search results. Store admins only need to fill in the Search Engine Unique ID to configure the extension. It supports features like autocomplete, image search, sorting results, and works across multiple Magento stores.
This document provides an overview and instructions for installing and configuring IBM Tivoli Web Access for Information Management. It discusses planning the installation, performing the SMP/E installation, customizing the Information Management installation, enabling access for users, and verifying the installation. The document is intended to help users install and set up Web Access to move an existing help desk application to the web. It contains information on installing and configuring necessary software and components, as well as customizing settings. Various sections provide details on tasks involved in the implementation and setup process.
Red hat enterprise_linux-5-installation_guide-en-usahmady
This document provides instructions for installing Red Hat Enterprise Linux 5 across several architectures, including x86, AMD64, Intel 64, Itanium, and IBM POWER systems. It covers starting the installation program, partitioning disks, setting network and time configuration, selecting packages to install, and completing the installation process. The document also includes troubleshooting tips for common installation issues.
This document is a study guide for the IBM Tivoli Configuration Manager 4.2 certification. It explains the certification path and prerequisites, provides an overview of the Tivoli Management Framework and Tivoli Configuration Manager components and installation, and includes sample test questions and answers to help readers prepare for the certification exam.
This document provides an overview of IBM InfoSphere Streams V3.0, which is a stream computing platform for performing real-time analytics on big data. It discusses key concepts of stream computing and InfoSphere Streams architecture. New features in V3.0 include improved configuration, administration, integration capabilities, and analytics toolkits. The document also covers deployment planning and creating Streams instances.
This document provides an introduction and overview of Intel Threading Building Blocks (TBB). It describes the library's benefits, including enabling task-based parallel programming rather than thread-based, targeting performance improvements, compatibility with other threading packages, emphasis on scalable and data parallel programming, and reliance on generic programming. The document structure is also outlined.
The document is a manual for Tivoli Business Systems Manager Version 2.1. It provides an overview of the product, which allows for end-to-end business impact management through integrated systems management. The manual details the product structure, components, functions, database structure, user interface, and planning requirements for implementation. It is intended to help users understand and implement the key capabilities of Tivoli Business Systems Manager.
This document provides an overview and comparison of IBM tape library solutions for backing up IBM xSeries servers. It discusses factors to consider when selecting a tape library such as capacity, number of drives, and scalability. It also provides configuration details for backing up to tape libraries using Tivoli Storage Manager, VERITAS Backup Exec, and CA ARCserve. Recovery procedures using the backup software and Tivoli Disaster Recovery Manager are also covered.
This document provides information about planning and deploying IBM TotalStorage Productivity Center for Data, including:
- An overview of the product, its features, architecture and supported levels
- Planning considerations for hardware, software, databases, user IDs and security
- Steps for installing the Agent Manager and other components on Windows and Linux
This document is the user manual for FLACS v9.0, a computational fluid dynamics (CFD) software for modeling fluid flow and chemical reactions. It describes the capabilities and proper use of FLACS, its preprocessor CASD, and postprocessor Flowvis. The manual provides guidance on installation, running simulations, working with files, and best practices for applications such as gas dispersion, explosions, fires, and more.
This document provides an overview of creating custom views in B4X. It discusses the structure of CustomView class modules, including predefined event declarations, designer properties, global variables, initialization routines, and routines for designer support and getting the base panel. Example code is provided for adding custom views by code, adding properties and events, and using custom views and properties in the designer. It also covers creating B4X libraries and compiling custom views to platform-specific libraries.
This document provides an overview and guidelines for developing workflows and automation packages for IBM Tivoli Intelligent Orchestrator V3.1. It discusses the architectural design of an automated provisioning solution using Tivoli Intelligent Orchestrator, including defining the scope and functionality of automation packages and workflows. It also provides practical guidance on topics like authentication, documentation standards, and setting up a development environment. The intended audience is IT professionals tasked with implementing automated provisioning and orchestration solutions using Tivoli Intelligent Orchestrator.
The document provides an introduction to artificial intelligence, including:
- A brief history of AI from the 1980s "AI winter" period of failed projects through to recent advances enabled by improved hardware and new research areas like machine learning.
- Knowledge representation and reasoning, rule engines, hybrid reasoning systems, and expert systems are introduced as key concepts in AI.
- The advantages of using a rule engine are discussed, as well as when rule engines are appropriate versus other approaches like scripting engines. The Rete algorithm, which is commonly used in rule engines, is also introduced.
This document describes the final version of the ClipFlair web platform, which consists of three areas: 1) The ClipFlair Studio learning area, 2) The ClipFlair Social Network workspace for learners and teachers, and 3) The collaboration workspace for project partners. It provides details on the goals, features, and technical implementation of each area. The platform allows users to create multimedia learning activities, collaborate socially, and manage project documents and communication.
The document provides an overview and installation instructions for integrating multiple IBM Tivoli products. It discusses security integration using LDAP and single sign-on. Product installations covered include IBM Service Management, Tivoli Monitoring, Tivoli Netcool, Tivoli Workload Scheduler, Tivoli Usage and Accounting Manager, and Tivoli Storage Productivity Center. The document is intended to help customers integrate these products in their environments.
This document provides instructions for installing and configuring IBM's Tivoli Intelligent ThinkDynamic Orchestrator software. It guides the reader through planning a demonstration of the software, installing necessary components on Windows systems, designing a sample data center model using XML, and loading and testing the model. The final chapter describes demonstrating the software's capabilities to monitor and manage resources and applications in the simulated data center.
This document provides a deployment guide for Tivoli Continuous Data Protection for Files. It discusses the product architecture including main components, capabilities, directories and files, and integration with IBM Tivoli Storage Manager. It covers planning considerations for deployment such as critical files, backup needs, backup locations, and file backup frequencies. The guide also describes installing, configuring, and using Tivoli Continuous Data Protection for Files as well as troubleshooting, use case scenarios, and how it can work with IBM Tivoli Storage Manager.
This chapter introduces network policies and Cisco access lists. Network policies are needed to implement security, robustness, and business policies on networks. Access lists are a key tool that network administrators can use on Cisco routers to implement these policies by controlling router resources, filtering packets, and filtering routing information. The chapter describes different types of network policies and provides an overview of how access lists can be used to achieve policy goals related to security, robustness, and business needs.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
4. 1 Git Extensions
Git Extensions is a toolkit aimed to make working with Git under Windows more intuitive. The shell
extension will integrate in Windows Explorer and presents a context menu on files and directories.
There is also a Visual Studio plug-in to use Git from Visual Studio. The source code of Git Extensions
is located here: http://github.com/spdr870/gitextensions/tree/master
1.1 Features
• Windows Explorer integration for Git
• Visual Studio (2005/2008/2010) plug-in for Git
• Feature rich user interface for Git
• Single installer installs Git, Git Extensions and the merge tool KDiff3
• 32bit and 64bit support
1.2 Video tutorials
There are video tutorials for some basic functions on YouTube.
• 1 Clone - Git Extensions - http://www.youtube.com/watch?v=TlZXSkJGKF8
• 2 Commit changes - http://www.youtube.com/watch?v=B8uvje6X7lo
• 3 Push changes - http://www.youtube.com/watch?v=JByfXdbVAiE
• 4 Pull changes - http://www.youtube.com/watch?v=9g8gXPsi5Ko
• 5 Handle merge conflicts - http://www.youtube.com/watch?v=Kmc39RvuGM8
5. 2 Getting started
2.1 Install
There is a single click installer that installs MSysGit, kdif3 and Git Extensions. The installer will detect
if 32bit and/or 64bit versions should be installed.
The installer can here: http://code.google.com/p/gitextensions/
Git Extensions depends heavily on MSysGit.
When MSysGit is not installed install this first.
Kdiff3 is optional, but is advised as a merge tool.
Choos the options to install.
Choose the SSH client to use. PuTTY is the
default because it has better windows integration.
6. 2.2 Settings
All settings will be verified when Git Extensions is started for the first time. If Git Extensions requires
any settings to be changed the settings dialog will be shown. All incorrect settings will be marked red.
You can ask Git Extensions to try to fix the setting for you by clicking on it.
All settings that are specific to Git Extensions will be stored in the Windows registry. The settings that
are used by Git are stored in the configuration files of Git. The global settings are stored in a file
called .gitconfig in the user directory. The local settings are stored in the .gitconfig file of the
repository.
The ‘Git Extension’ tab contains all settings needed for Git Extension to run properly. The path to
git.cmd and git.exe can be set here. This is only needed when these are not in the system path.
Path to run git (git.cmd or Needed for Git Extensions to run Git commands. Set the full path to
git.exe) git (msysgit or cygwin).
Path to git.exe Only needed for a few optimized commands
Limit number of commits that Git Extensions uses lazy loading to load the commit log. Lower this
will be loaded in list at start-up. number to increase the start-up speed. Increase the number for
faster scrolling. Turn of revision graph for optimal result!
Show revision graph in commit Turn revision graph in commit log on/off.
log.
Show Git command line dialog Turn this option on if you want to see the Git command line dialog
when executing process. when a process is executed.
Dictionary for spelling checker Choose the dictionary to use for the spelling checker in the commit
dialog.
Smtp server for sending patches Smtp server to use for sending patches
Use FileSystemWatcher to Using the FileSystemWatcher to check index state improves the
check if index is changed performance is some cases. Turn this off if you experience refresh
problems in commit log.
Show relative date instead of full Show relative date, e.g. 2 weeks ago, instead of full date.
date.
Follow renames in file history Try to follow file renames in the file history.
Encoding Choose the encoding you want GitExtensions to use
7. The items on the Start Page can be edited. In this tab you can add and remove categories. Per
category you can either configure a RSS feed or add repositories. The order can be changed using the
context menus in the Start Page.
In the appearance tab the following items can be set:
Revision graph colors The colors that are used in the revision graph
Difference view colors The colors that are used to mark changes
Application Icon The color of the application icon. This is useful for recognising
various open instances.
Author images Enable or disable downloading author images from gravatar.com.
8. With the “Clear image cache” the cached items can be removed.
In the ‘Global settings’ tab some global Git settings can be set.
User name User name shown in commits and patches
User email User email shown in commits and patches
Editor Editor that git.exe opens (e.g. for editing commit message). This is
not used by Git Extensions, only when you call git.exe from the
command line. By default Git will use the command line text editor vi.
Mergetool Merge tool used to solve merge conflicts. Git Extensions will search
for common merge tools on your system.
Path to mergetool Path to merge tool. Git Extensions will search for common merge
tools on your system.
Mergetool command Command that Git uses to call the merge tool. Git Extensions will try
to set this automatic when a merge tool is chosen. This setting can
be left empty when Git supports the mergetool (e.g. kdiff3)
DiffTool DiffTool that is used
Path to DiffTool The path to the difftool.
DiffToolCommand Command that Git uses to start the DiffTool. This setting should only
be filled when Git doesn't support the mergetool.
9. In the tab ‘SSH’ you can configure the SSH client you want Git to use. Git Extensions is optimized for
PuTTY. Git Extensions will show command line dialogs if you do not use PuTTY and user input is
required. Git Extensions can load SSH keys for PuTTY when needed.
10. 2.3 Start Page
The start page contains the most common tasks, recently opened repositories and favourites. The left
side of the start page is static. The other items can be edited.
Repositories can be moved to favourites using the context menu. Choose edit to add new repositories
to any category.
11. 2.4 Clone existing repository
You can clone an existing repository using the ‘Clone’ menu option. You can choose the repository
type to clone to. For personal use you need to choose ‘Personal repository’. For a central or public
repository, choose ‘Central repository’. A central repository does not have a working directory.
12. 2.5 Create new repository
When you do not want to work on an existing project, you can create your own repository. Choose the
menu option ‘Init new repository’ to create a new repository.
You can choose to create a Personal repository or a Central repository. A personal repository looks
the same as a normal working directory but has a directory named .git on root level containing the
version history. This is the most common repository.
Central repositories only contain the version history. Because a central repository has no working
directory you cannot checkout a revision in a central repository. It is also impossible to merge or pull
changes is a central repository. This repository type can be used as a public repository where
developers can push changes to or pull changes from.
13. 3 Browse repository
You can browse a repository by starting Git Extensions and select the repository to open. The main
window contains the commit log. You could also open the ‘Browse’ window from the shell extensions
and from the Visual Studio IDE.
3.1 View commit log
The full commit history can be browsed. There is a graph that shows branches and merges. You can
show the difference between two revision by selection them using ctrl-click.
In the context menu of the commit log you can enable or disable the revision graph. You can also
choose to only show the current branch instead of showing all branches. The other options will be
discussed later.
14. 3.2 Search history
The history can be searched using regular expressions are basic search terms. The quick filter in the
toolbar searches in the commit message, the author and the committer.
In the context menu of the commit log you can open the advanced filter dialog. The advanced filter
dialog allows you to search for more specific commits. To remove the filter either remove the filter in
the toolbar and press enter or remove the filter in the advanced filter dialog.
15. 3.3 Singe file history
The single file history viewer shows all revisions of a single file. You can view the content of the file in
after each commit in the ‘View’ tab.
You can view the difference report from the commit in the ‘Diff’ tab. Added lines are marked with a ‘+’,
removed lines are marked with a ‘–‘.
16. 3.4 Blame
There is a blame function in the file history browser. It shows the last person editing a single line.
Double clicking on a code line shows the full commit introducing the change.
17. 4 Commit
A commit is a set of changes with some extra information. Every commit contains the follow
information:
• Changes
• Committer name and email
• Commit date
• Commit message
• Cryptographically strong SHA1 hash
Each commit creates a new revision of the source. Revisions are not tracked per file; each change
creates a new revision of the complete source. Unlike most traditional source control management
systems, revisions are not named using a revision number. Each revision is named using a SHA1, a
41 long characters cryptographically strong hash.
4.1 Commit changes
Changes can be committed to the local repository. Unlike most other source control management
systems you do not need to checkout files before you start editing. You can just start editing files, and
review all the changes you made in the commit dialog later. When you open de commit dialog, all
changes are listed in the top-left.
There are three kinds of changes:
Untracked This file is not yet tracked by Git. This is probably a new file, or a file that has not
been committed to Git before.
Modified This file is modified since the last commit.
Deleted This file has been deleted.
18. When you rename or move a file Git will notice that this file has been moved, but currently Git
Extensions does not show this in the commit dialog. Occasionally you will need to undo the file
change. This can be done in the context menu of any unstaged file.
During your initial commit there are probably lots of files you do not want to be tracked. You can ignore
these files by not staging them, but they will show every time. You could also add them to the
.gitignore file of you repository. Files that are in the .gitignore file will not show up in the commit dialog
again. You can open the .gitignore editor from the menu ‘Working dir changes’.
You need to stage the changes you want to commit by pressing the ‘Stage selected files’ button. You
also need to stage deleted files because you stage the change and not the file. When all the changes
you want to commit are staged, enter a commit message and press the commit button.
19. It is also possible to add files to you last commit using the ‘Amend to last commit’ button. This can be
very useful when you forgot some changes. This function rewrites history; it deletes the last commit
and commits it again including the added changes. Make sure you only use ‘Amend to last commit’
when the commit is not yet published to other developers.
There is a build in spelling checker that checks the commit message. Incorrect spelled words are
underlined with a red wave line. By right-clicking on the misspelled word you can choose the correct
spelling or one of the other options.
Git Extensions installs a number of dictionaries by default. You can choose another language in the
context menu of the spelling checker or in the settings dialog. To add a new spelling dictionary add the
dictionary file to the 'Dictionaries' folder inside the Git Extensions installation folder.
20.
21. 4.2 Cherry pick commit
A commit can be recommitted by using the cherry pick function. This can be very useful when you
want to make the same change on multiple branches.
4.3 Revert commit
A commit cannot be deleted once it is published. If you need to undo the changes made in a commit,
you need to create a new commit that undoes the changes. This is called a revert commit.
22. 4.4 Stash changes
If there are local changes that you do not want to commit yet and not want to throw away either, you
can temporarily stash them. This is useful when working on a feature and you need to start working on
something else for a few hours. You can stash changes away and then reapply them to your working
dir again later. Stashes are typically used for very short periods.
You can create multiple stashes if needed. Stashes are shown in the commit log with the text [stash].
The stash is especially useful when pulling remote changes into a dirty working directory. If you want a
more permanent stash, you should create a branch.
23. 5 Tag
Tags are used to mark a specific version. Usually a tag will not be moved anymore. The image below
shows the commit log of Git Extensions with to tags indicating version [1.08] and [1.06].
5.1 Create tag
In Git Extensions you can tag a revision by choosing ‘Create new tag’ in the commit log context menu.
A dialog will prompt for the name of the tag. You can also choose ‘Create tag’ from the ‘Commands’
menu, which will show a dialog to choose the revision and enter the tag name.
Once a tag is created, it cannot be moved again. You need to delete the tag and create it again to
move it.
5.2 Delete tag
For some operation it is very useful to create tags for temporary usage. Git uses SHA1 hashes to
name each commit. When you want to merge with an unnamed branch it is good practise to tag the
unnamed branch, merge with the tag and then delete the tag again.
24. 6 Branches
Branches are used to commit changes separate from other commits. It is very
common to create a branch when you start working on a feature and you are not sure
if this feature will be finished in time for the next release. The image on the right
illustrates a branch created on top of commit B.
In Git branches are created very often. Creating a branch is very easy to do and it is
recommended to create a branch very often. In fact, when you make a commit to a
cloned repository you start a new branch. I will explain this in the pull chapter.
You can check on what branch you are working in the toolbar.
6.1 Create branch
In Git Extensions there are multiple ways to create a new branch. In the image below I create a new
branch from the context menu in the commit log. This will create a new branch on the revision that is
selected.
I will create a new branch called ‘Refactor’. In this branch I can do whatever I want without considering
others. In the ‘Create branch’ dialog there is a checkbox you can check if you want to checkout this
branch immediate after the branch is created.
When the branch is created you will see the new branch [Refactor] in the commit log. If you chose to
checkout this branch the next commit will be committed to the new branch.
Creating branches in Git requires only 41 bytes of space in the repository. Creating a new branch is
very easy and is very fast. The complete work flow of Git is optimized for branching and merging.
6.2 Checkout branch
You can switch from the current branch to another branch using the checkout command. Checkout a
branch sets the current branch and updates all sources in the working directory. Uncommitted
changes in the working directory can be overwritten, make sure your working directory is clean.
25. 6.3 Merge branches
In the image below there are two branches, [Refactor] and [master]. We can merge the commits from
the master branch into the Refactor. If we do this, the Refactor branch will be up to date with the
master branch, but not the other way around. As long as we are working on the Refactor branch we
cannot tough the master branch itself. We can merge the sources of master into our branch, but
cannot make any change to the master branch.
To merge the Refactor branch into the master branch, we need to switch to the master branch first.
Once we are on the master branch we can choose merge by choosing ‘Merge branches’ from the
‘Commands’ menu. In the merge dialog you can check the branch you are working on. After selected
the branch to merge with, click the ‘Merge’ button.
26. After the merge the commit log will show the new commit containing the merge. Notice that the
Refactor branch is not changed by this merge. If you want to continue working on the Refactor branch
you can merge the Refactor branch with master. You could also delete the Refactor branch if it is not
used anymore.
When you need to merge with on unnamed branch you can use a tag to give it a temporary name.
6.4 Rebase branch
The rebase command is the most complex command in Git. The rebase command is very similar to
the merge command. Both rebase and merge are used to get a branch up-to-date. The main
difference is that rebase can be used to keep the history linear contrary to merges.
A rebase of Refactor on top of master will perform the following actions:
• All commits specific to the Refactor branch will be stashed in a temporary location
• The branch Refactor will be removed
• The branch Refactor will be recreated on the master branch
• All commits will be recommitted in the new Refactor branch
During a rebase merge conflicts can occur. You need to solve the merge conflicts for each commit that
is rebased. The rebase function in Git Extensions will guide you through all steps needed for a
successful rebase.
27. The image below shows the commit log after the rebase. Notice that the history is changed and is
seems like the commits on the Refactor branch are created after the commits on the master branch.
Because this function rewrites history you should only use this on branches that are not published to
other repositories yet. When you rebase a branch that is already pushed it will be harder to pull or
push to that remote. If you want to get a branch up-to-date that is already published you should merge.
6.5 Delete branch
It is very common to create a lot of branches. You can delete branches when they are not needed
anymore and you do not want to keep the work done in that branch. When you delete a branch that is
not yet merged, all commits will be lost. When you delete a branch that is already merged with another
branch, the merged commits will not be lost because they are also part of another branch.
You can delete a branch using ‘Delete branch’ in ‘Commands’ menu. If you want to delete a branch
that is not merged into another branch, you need to check the ‘Force delete’ checkbox.
28. 7 Patches
Every commit contains a change-set, a commit date, the committer name, the commit message and a
cryptograph SHA1 hash. Local commits can be published by pushing it to a remote repository. To be
able to push you need to have sufficient rights and you need to have access to the remote repository.
When you cannot push directly you can create patches. Patches can be e-mailed to someone with
access to the repository. Each patch contains an entire commit including the commit message and the
SHA1.
7.1 Create patch
Format a single patch or patch series using the format patch dialog. You need to select the newest
commit first and then select the oldest commit using ctrl-click. You can also select an interrupted patch
series, but this is not recommended because the files will not be numbered.
29. When the patches are created successfully the following dialog will appear.
7.2 Apply patches
It is possible to apply a single patch file or all patches in a directory. When there are merge conflicts
applying the patch you need to resolve them before you can continue. Git Extensions will help you
applying all patches by marking the next recommended step.
30. 8 Remote features
Git is a distributed source control management system. This means that all changes you make are
local. When you commit changes, you only commit them to your local repository. To publish your local
changes you need to push. In order to get changes committed by others, you need to pull.
8.1 Manage remote repositories
You can manage the remote repositories in the ‘Remotes’ menu.
When you cloned your repository from a public repository, this remote is already configured. You can
rename each remote for easy recognition. The default name after cloning a remote is ‘origin’. If you
use PuTTY as SSH client you can also enter the private key file for each remote. Git Extensions will
load the key when needed. How to create a private key file is described in the next paragraph.
In the ‘Default pull behaviour’ tab you can configure the branches that need to be pulled and merged
by default. If you configure this correctly you will not need to choose a branch when you pull or push.
There are two buttons on this dialog:
Prune remote branches Throw away remote branches that do not exist on the remote
anymore
Update all remote branch info Fetch all remote branch information
After cloning a repository you do not need to configure all remote branches manually. Instead you can
checkout the remote branch and choose to create a local tracking branch.
31. 8.2 Create SSH key
Git uses SSH for accessing private repositories. SSH uses a public/private key pair for authentication.
This means you need to generate a private key and a public key. The private key is stored on your
computer locally and the public key can be given to anyone. SSH will encrypt whatever you send using
your secret private key. The receiver will then use the public key you send to decrypt the data.
This encryption will not protect the data itself but it protects the authenticity. Because the private key is
only available to the sender, the receiver can be sure about the origin of the data. In practise the key
pair is only used for the authentication process. The data itself will be encrypted using a key that is
exchanged during this initial phase.
8.2.1 PuTTY and github
PuTTY is SSH client that for Windows that is a bit more user friendly then OpenSSH. Unfortunately
PuTTY does not work with all servers. In this paragraph I will show how to generate a key for github
using putty.
First make sure GitExtensions is configured to use PuTTY and all paths are correct.
In the Remotes menu you can choose “Generate or import key” to start the key generator.
32. PuTTY will ask you to move the mouse around to generate a more random key. When the key is
generated you can save the public and the private key in a file. You can choose to protect the private
key with a password but this is not necessary.
Now you have a key pair you need to give github the public key. This can be done in “Account
Settings” in the tab “SSH Public Keys”. You can add multiple keys here, but you only need one key for
all repositories.
After telling github what public key to use to decrypt, you need to tell GitExtensions what private key to
use to encrypt. In the clone dialog there is a “Load SSH key” button to load the private key into the
PuTTY authentication agent. This can also be done manually by starting the PuTTY authentication
agent and choose “add key” in the context menu in the system tray.
33. GitExtensions can load the private keys automatically for you when communicating with a remote. You
need to configure the private key for the remote. This is done in the “Manage remote repositories”
dialog.
8.2.2 OpenSSH and github
When you choose to use OpenSSH you need to configure GitExtensions as shown in the screenshot
below.
OpenSSH is the best SSH client there is but it lacks Windows support. Therefore it is slightly more
complex to use. Another drawback is that GitExtensions cannot control OpenSSH and needs to show
the command line dialogs when OpenSSH might be used. GitExtensions will show the command line
window for every command that might require a SSH connection. For this reason PuTTY is the
prefered SSH client in GitExtensions.
To generate a key pair in OpenSSH you need to go to the command line. I recommend to use the git
bash because the path to OpenSSH is already set.
34. Type the following command: ssh-keygen -C “your@email.com” -t rsa
Use the same email address as the email address used in git. You will be asked where if you want to
protect the private key with a password. This is not necessary. By default the public and private keys
are stored in “c:Documents and Settings[User].ssh” or “c:Users[user].ssh”.
You do not need to tell GitExtensions about the private key because OpenSSH will load it for you. Now
open the public key using notepad and copy the key to github. This can be done in “Account Settings”
in the tab “SSH Public Keys” on http://www.github.com.
8.3 Pull changes
You can get remote changes using the pull function. Before you can pull remote changes you need to
make sure there are no uncommitted changes in your local repository. If you have uncommitted
changes you should commit them or stash them during the pull. You can read about how to use the
stash in the Stash chapter.
35. In order to get your personal repository up-to-date, you need to fetch changes from a remote
repository. You can do this using the ‘Pull’ dialog. When the dialog starts the default remote for the
current branch is set. You can choose another remote or enter a custom url if you like. When the
remote branches configured correctly, you do not need to choose a remote branch.
If you just fetch the commits from the remote repository and you already committed some changes to
your local repository, the commits will be in a different branch. In the pull dialog this is illustrated in the
image on the left. This can be useful when you want to review the changes before you want to merge
them with your own changes.
36. When you choose to merge the remote branch after fetching the changes a branch will be created,
and will be merged you’re your commit. Doing this creates a lot of branches and merges, making the
history harder to read.
Instead of merging the fetched commits with your local commits, you can also choose to rebase your
commits on top of the fetched commits. This is illustrated on the left in the image below. A rebase will
first undo your local commits (c and d), then fetch the remote commits (e) and finally recommit your
local commits. When there is a merge conflict during the rebase, the rebase dialog will show.
Next to the pull button there are some buttons that can be useful:
Solve conflicts When there are merge conflicts, you can solve them by pressing this button.
Stash changes When the working dir contains uncommitted changes, you need to stash them
before pulling.
Auto stash Check this checkbox if you want to stash before pulling. The stash will be
reapplied after pulling.
Load SSH key This button is only available when you use PuTTY as SSH client. You can
press this button to load the key configured for the remote. If no key is set, a
dialog will prompt for the key.
37. 8.4 Push changes
In the browse window you can check if there are local commits that are not pushed to a remote
repository yet. In the image below the green labels mark the position of the master branch on the
remote repository. The red label marks the position of the master branch on the local repository. The
local repository is ahead three commits.
To push the changes press ‘Push’ in the toolbar.
The push dialog allows you to choose the remote repository to push to. The remote repository is set to
the remote of the current branch. You can choose another remote or choose a url to push to. You can
also specify a branch to push.
Tags are not pushed to the remote repository. If you want to push a tag you need to open the `Tags`
tab in the dialog. You can choose to push a singe tag or all tags. No commits will be pushed when the
`Tags` tab is selected, only tags.
You can not merge your changes in the remote repository. Merging must be done locally. This means
that you cannot push your changes before the commits are merged locally. In practice you need to pull
before you can push most of the times.
38. 9 Merge conflicts
When merging branches or commits you can get merge conflicts. Git will try to resolve these, but
some conflicts need to be resolved manually. Git Extensions will show warnings when there is a
merge conflict.
9.1 Handle merge conflicts
To solve merge conflicts just click on a warning or open the merge conflict dialog from the menu. A
dialog will prompt showing all conflicts. You can solve a conflict by double-click on a filename.
There are three kinds of conflicts:
File deleted and changed Use modified or deleted file?
File deleted and created Use created or deleted file?
File changed both locally and remotely Start merge tool.
If the file is deleted in one commit and changed in another commit, a dialog will ask to keep the
modified file or delete the file. When there is a conflicting change the merge tool will be started. You
can configure the tool you want to use for merge conflicts. The image below shows Perforce P4Merge
a free to use merge tool. Git Extensions is packaged with KDiff3, an open source merge tool.
In the merge tool you will see four versions of the same file:
Base The latest version of the file that exist in both repositories
Local The latest local version of the file
Remote The latest remote version of the file
Merged The result of the merge
When you are in the middle of a merge the file named local represents your file. When you are in the
middle of a rebase the file named remote represents your file. This can be confusing, so double check
if you are in doubt.
39.
40. 10 Submodules
Large projects can be split into smaller parts using submodules. A submodule contains the name, url
and revision of another repository. To create a submodule in an existing git repository you need to add
a link to another repository containing the files of the submodule.
10.1 Manage submodules
The current state of the submodules can be viewed with the ‘Manage submodules’ function. All
submodules are shown in the list on the left.
Add submodule Add a new submodule to the repository
Synchronize Synchronizes the remote URL configuration setting to the value specified in
.gitmodules for the selected submodule.
Initialize Initialize the selected submodules, i.e. register each submodule name and url
found in .gitmodules into .git/config. The submodule will also be updated.
Update Update the registered submodules, i.e. clone missing submodules and checkout
the commit specified in the index of the containing repository.
41. 10.2 Add submodule
To add a new submodule choose ‘Add submodule’ in the ‘Manage submodules’ dialog.
Path to submodule Path to the remote repository to use as submodule.
Local path Local path to this submodule, relative to the root of the current repository.
Branch Branch to track
42. 11 Maintenance
In this chapter some of the functions to maintain a repository are discussed.
11.1 Compress Git database
Git will create a lot of files. You can run the ‘Compress git database’ to pack all small files building up a
repository into one big file. Git will also garbage collect all unused objects that are older then 15 days.
When a database is fragmented into a many small files compressing the database can increase
performance.
11.2 Recover lost objects
If you accidently deleted a commit you can try to recover it using the `Recover lost objects´ function. A
dialog will show you all dangling objects and will allow you to review and recover them.
Normally Git will not delete files right away when you remove something from your repository. The
reason for this is that you can restore deleted items if you need to. Git will delete removed items when
they are older then 15 days and you run ‘Compress git database’.
There are several functions to help you find the lost items. By default Git Extensions will only show
commits. To show all items, just uncheck the 'Show only commits' option. The other options can be
checked/unchecked to get more/less results. Double-click on on item to view the content. When you
located the item you want to recover you can tag it using the 'Tag selected object' button.
Git Extensions also is able to tag all lost objects. Doing this will make all lost objects visible again
making it very easy to locate the commit(s) you would like to recover. After recovering a commit using
the 'Tag all lost commits' button, you can remove all tags using the 'Delete all LOST_AND_FOUND
tags' button.
43.
44. 11.3 Fix user names
When someone accidentally committed using a wrong username this can be fixed using the ‘Edit
.mailmap’ function. Git will use the username for an email address when it is set in the .mailmap file.
Fix user name using commit email:
Proper Name <commit@email.xx>
Fix email address using commit email:
<proper@email.xx> <commit@email.xx>
Fix email address and name using commit email:
Proper Name <proper@email.xx> <commit@email.xx>
Fix email address and name using commit name and email
Proper Name <proper@email.xx> Commit Name <commit@email.xx>
45. 11.4 Ignore files
Git will track all files that are in the working directory. Normally you do not want to exclude all files that
are created by the compiler. You can add files that should be ignored to the .gitignore file. You can use
wildcards and regular expressions. All entries are case sensitive. The button ‘Add default ignores’ will
add files that should be ignored when using Visual Studio.
A short overview of the syntax:
# Lines started with '#' are handled as comments
! Lines started with '!' are exclude patterns
[Dd] Characters inside [..] means that 1 of the characters must match
* Wildcard
/ A leading slash matches the beginning of the pathname; for example, "/*.c" matches
"cat-file.c" but not "mozilla-sha1/sha1.c"
/ If the pattern ends with a slash, it is removed for the purpose of the following
description, but it would only find a match with a directory. In other words, foo/ will
match a directory foo and paths underneath it, but will not match a regular file or a
symbolic link foo (this is consistent with the way how pathspec works in general in git).
For more detailed information:
http://www.kernel.org/pub/software/scm/git/docs/gitignore.html
46. 12 Translations
12.1 Change language
In the settings dialog a translation can be chosen. The translation files are located in a directory
located in the Git Extensions installation directory. The files are readable xml files.
12.2 Translate Git Extensions
The application has a build in translation tool to help create and edit translations. To open the
translation tool choose “Translate” in the “Help” menu.
The functions of the translation tool are described in the image below. To contribute any translations
you can either e-mail a patch or send a pull request using github.
47. 13 Integration
During installation you can choose to install the Visual Studio plug-in and shell extensions.
13.1 Visual Studio
There are two options in the context menu on files.
- View the file history by choosing the ‘File history’ option.
- Reset the file changes to the last committed revision.
A Git Extensions toolbar allows you to perform the most common actions.
Commit
Browse
Pull
Push
Stash changes
Settings
Almost all function can be started from the ‘Git’ menu in Visual Studio.
48.
49. 13.2 Windows Explorer
The common commands can be started from Windows Explorer using the shell extensions. This
option is only available when Shell Extensions are installed.
50. 14 Command line
14.1 Git Extensions command line
Most features can be started from the command line. It is recommended to add gitex.cmd to the path
when using from the command line.
51. The following functions are available from the command line:
• Add files
• Apply patches
• Archive
• Create branches/tags
• Checkout branches/tags/revisions
• Merge branches
• Rebase
• Commit changes
• Stash changes, with multiple stash support
• Clone repositories
• Push
• Pull
• SSH support
• All Git remote features
• Init new repository
• Single file history
• Full development history
• Difference reports
• Browsing repository
• Support for external mergetools
52. Git Cheat Sheet Apply patch without merging
$ git apply c:/patch/0001-employee.patch
Create new repository Merge patch
$ git init $ git am - –3way –-signoff c:/patch/0001-employee.patch
Create shared repository Solve conflicts (add --tool=kdiff3 if no mergetool is specified)
$ git init –-bare –-shared=all $ git mergetool
Clone repository $ git am –-3way - –resolved
$ git clone c:/demo1 c:/demo2
Stash changes
Checkout branch $ git stash
$ git checkout <name> Apply stashed changes
Create branch $ git stash apply
$ git branch <name> Pull changes (add --rebase to rebase instead of merge)
Delete branch $ git pull c:/demo1 master
$ git branch - d <name> Solve conflicts (add --tool=kdiff3 if no mergetool is specified)
Merge branch (from the branch to merge into) $ git mergetool
$ git merge PDC $ git commit
Solve conflicts (add --tool=kdiff3 if no mergetool is specified) Push changes (in branch $ git push c:/demo1 master master:<new>)
$ git mergetool $ git push c:/demo1
$ git commit
Blame
Create tag $ git blame –M –w <filename>
$ git tag <name>
Help
Add files/changes (. for all files) $ git <command> - - help
$ git add .
Commit added files/changes (--amend to amend to last commit) Default names
$ git commit –m “Enter commit message” master : default branch
origin : default upstream repository
Discard changes HEAD : current branch
$ git reset - - hard HEAD^ : parent of HEAD
HEAD~4 : the great-great grandparent of HEAD
Create patch (-M = detect renames –C = detect copies)
$ git format- patch –M –C origin