Open-source News

Weston, the reference compositor to Wayland, is out today with a big feature update. Most exciting is preparation work for better supporting HDR monitors moving forward as well as preparing for multi-GPU and multi-back-end use-cases...

Earlier this month Blender 3.3 released and in addition to introducing an Intel oneAPI back-end, it's notable for bringing improvements to the AMD HIP back-end for Radeon GPUs. Significant on the AMD side is extending GPU support back to GFX9/Vega. Thus it's a good time for a fresh round of benchmarking for showing how the AMD Radeon HIP performance against that of NVIDIA's existing CUDA and OptiX back-ends.

How to Transcode FLAC Files With flac2all in Linux  Make Tech Easier

A New Linux Tool Aims to Guard Against Supply Chain Attacks  WIRED

1. A New Linux Tool Aims to Guard Against Supply Chain Attacks  WIRED
2. Wolfi: A Linux undistro with security measures for the software supply chain  Help Net Security
3. Software supply chain security gets its first Linux distro, Wolfi  TechRepublic
4. Wolfi Linux is designed to safeguard the software supply chain  BetaNews
5. Wolfi Linux (Un)Distribution Secures The Software Supply Chain  iProgrammer
6. View Full Coverage on Google News

Senior Linux Storage Engineer - High-Performance Computing News Analysis | insideHPC  insideHPC

Fwupd 1.8.5 is out today for continuing to improve the firmware updating experience on Linux systems in conjunction with the Linux Vendor Firmware Service (LVFS)...

Linux Mint 21 Vanessa: Everything You Need To Know  BollyInside

EuroLinux Desktop is an RHEL-based Distro With Enterprise Perks  It's FOSS News

While Intel's Compute-Runtime stack is fully open-source and already provides OpenCL 3.0 support for recent generations of Intel graphics under Linux, it looks like the recently-merged "Rusticl" Rust OpenCL implementation in Mesa will soon be working too on Intel graphics hardware as an alternative OpenCL 3.0 implementation...

How to backup directly to Mega on Linux  AddictiveTips

Microsoft and Canonical bring systemd support to Windows Subsystem for Linux  BetaNews

A Microsoft engineer has landed an improvement to the Mesa Gallium3D Video Acceleration "VA" state tracker that can allow for faster video processing times and greater GPU utilization...

Google engineers on Wednesday released AOM-AV1 3.5 as the newest version of their open-source AV1 video encoder. With AOM-AV1 3.5 comes yet more performance improvements as well as memory optimizations...

Get a whole lot of Serious Sam in this game bundle  GamingOnLinux

The first alpha release of the Debian Installer to be used by Debian 12 "Bookworm" is now available for early testing...

Turnip as the Mesa Vulkan driver for Qualcomm Adreno graphics is now able to support Vulkan 1.3...

Debian GNU/Linux 12 “Bookworm” Installer Adds Windows 11 Detection, New ARM Devices  9to5Linux

How to install Qcad on Debian 11 Bullseye  Linux Shout

5 Git configurations I make on Linux Alan Formy-Duval Thu, 09/22/2022 - 03:00

Setting up Git on Linux is simple, but here are the five things I do to get the perfect configuration:

1. Create global configuration
2. Set default name
3. Set default email address
4. Set default branch name
5. Set default editor

I manage my code, shell scripts, and documentation versioning using Git. This means that for each new project I start, the first step is to create a directory for its content and make it into a Git repository:

$ mkdir newproject
$ cd newproject
$ git init

More on Git What is Git? Git cheat sheet Markdown cheat sheet New Git articles

There are certain general settings that I always want. Not many, but enough that I don't want to have to repeat the configuration each time. I like to take advantage of the global configuration capability of Git.

Git offers the git config command for manual configuration but this is a lot of work with certain caveats. For example, a common item to set is your email address. You can set it by running git config user.email followed by your email address. However, this will only take effect if you are in an existing Git directory:

$ git config user.email alan@opensource.com
fatal: not in a git directory

Plus, when this command is run within a Git repository, it only configures that specific one. The process must be repeated for new repositories. I can avoid this repetition by setting it globally. The --global option will instruct Git to write the email address to the global configuration file; ~/.gitconfig, even creating it if necessary:

  Remember, the tilde (~) character represents your home directory. In my case that is /home/alan. $ git config --global user.email alan@opensource.com
$ cat ~/.gitconfig
[user]
        email = alan@opensource.com

The downside here is if you have a large list of preferred settings, you will have a lot of commands to enter. This is time-consuming and prone to human error. Git provides an even more efficient and convenient way to directly edit your global configuration file—that is the first item on my list!

1. Create global configuration

If you have just started using Git, you may not have this file at all. Not to worry, let's skip the searching and get started. Just use the --edit option:

$ git config --global --edit

If no file is found, Git will generate one with the following content and open it in your shell environment's default editor:

# This is Git's per-user configuration file.
[user]
# Please adapt and uncomment the following lines:
#       name = Alan
#       email = alan@hopper
~
~
~
"~/.gitconfig" 5L, 155B                                     1,1           All

Now that we have opened the editor and Git has created the global configuration file behind the scenes, we can continue with the rest of the settings.

2. Set default name

Name is the first directive in the file, so let's start with that. The command line to set mine is git config --global user.name "Alan Formy-Duval". Instead of running this command, just edit the name directive in the configuration file:

name = Alan Formy-Duval3. Set default email address

The email address is the second directive, so let's update it. By default, Git uses your system-provided name and email address. If this is incorrect or you prefer something different, you can specify it in the configuration file. In fact, if you have not configured them, Git will let you know with a friendly message the first time you commit:

Committer: Alan <alan@hopper>
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate....

The command line to set mine is git config --global user.email "alan@opensource.com". Instead, edit the email directive in the configuration file and provide your preferred address:

email = alan@opensource.com

The last two settings that I like to set are the default branch name and the default editor. These directives will need to be added while you are still in the editor.

4. Set default branch name

There is currently a trend to move away from the usage of the word master as the default branch name. As a matter of fact, Git will highlight this trend with a friendly message upon initialization of a new repository:

$ git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>

This directive, named defaultBranch, needs to be located in a new section named init. It is now generally accepted that many coders use the word main for their default branch. This is what I like to use. Add this section followed by the directive to the configuration:

More Linux resources Linux commands cheat sheet Advanced Linux commands cheat sheet Free online course: RHEL technical overview Linux networking cheat sheet SELinux cheat sheet Linux common commands cheat sheet What are Linux containers? Our latest Linux articles [init]
            defaultBranch = main5. Set default editor

The fifth setting that I like to set is the default editor. This refers to the editor that Git will present for typing your commit message each time you commit changes to your repository. Everyone has a preference whether it is nano, emacs, vi, or something else. I'm happy with vi. So, to set your editor, add a core section that includes the editor directive:

[core]
            editor = vi

That's the last one. Exit the editor. Git saves the global configuration file in your home directory. If you run the editing command again, you will see all of the content. Notice that the configuration file is a plain text file, so it can also be viewed using text tools such as the cat command. This is how mine appears:

$ cat ~/.gitconfig
[user]
        email = alan@opensource.com
        name = Alan Formy-Duval
[core]
        editor = vi
[init]
        defaultBranch = main

This is a simple guide to quickly get started working with Git and a few of its many configuration options. There are many other articles on Git here at Opensource.com, as well as our downloadable Git cheat sheet.

This is a simple guide to quickly get started working with Git and a few of its many configuration options.

Linux Git What to read next This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.