10000 Proposal: Add new git commands to ProGit · Issue #1572 · progit/progit2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Proposal: Add new git commands to ProGit #1572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
SetTrend opened this issue Dec 3, 2020 · 6 comments
8000 Open

Proposal: Add new git commands to ProGit #1572

SetTrend opened this issue Dec 3, 2020 · 6 comments

Comments

@SetTrend
Copy link
SetTrend commented Dec 3, 2020 •
edited
Loading

Recently, the git team introduced a number of new commands (e.g. git switch or git restore), plus, a new hash algorithm has been introduced.

I'd like to propose to update the book to accommodate the new commands.



Excellent book, by the way.
@HonkingGoose
Copy link
Contributor

Hi @SetTrend, thanks for opening a issue.

Good to hear that you like the book. 👍

The ProGit2 team has already discussed including the new commands git switch and git restore, you can follow issue #1529 and #1524 for progress on that. 😉
In short: we're waiting until macOS and Debian stable update their Git versions before we do a big rewrite to use the newer commands in the text.

We do cover git restore and git switch already, see #1511 and #1523 that added a section on git restore and a tip mentioning git switch.

The Git SHA256 commit hashing is still in experimental support, and you can't use it on GitHub or anywhere else yet. So I think including it already is a bit soon, but that's up to the ProGit2 team to decide. 😄

Covering the new SHA256 hashes will also mean that the book needs new text and new pictures, so that's a lot of work. It's basically a full rewrite of the book at that stage, I think.

@SetTrend
Copy link
Author
SetTrend commented Dec 5, 2020 •
edited
Loading

So, you've already got plans for the new commands - that's great news! ❤️

I very much liked the style of writing the book has been written in. Things were so well explained, it has been a joy reading it. I hope the original author will have time to contribute to the new version, too.

So, since my request has already been dealt with ... if you don't require this issue for your own respository purposes, please close it to your liking.

@max123kl
Copy link
Contributor
max123kl commented Dec 5, 2020

In short: we're waiting until macOS and Debian stable update their Git versions ...

BTW:
If you want to use a newer git version with Debian, you have to use the repositories "debian-updates" and/or "debian-backports".
As far as I know the package versions are not upgraded within a master release (except security updates).
So a newer git version can be expected with Debian-11/Bullseye (probably mid 2021).

If you want or need to use a newer git version, you have to configure your "sources.list" file and possibly the "preferences" file in the /etc/apt directory accordingly.

A corresponding note could be included in the ProGit2 book.

@bagasme
Copy link
Contributor
bagasme commented Jan 20, 2021

@max123kl AFAIK debian-updates contain bugfixes to Git distributed in Debian, not latest version (one have to use Debian Sid or Testing for that).

@max123kl
Copy link
Contributor
max123kl commented Jan 20, 2021 •
edited
Loading

@bagasme
It is not necessary to install Debian Sid or Testing if you want to use some packages in a newer version than "stable" provides. Currently, the Git packages are included in buster-backports in version 1:2.29.2-1~bpo10+1.
The procedure to set this up is apt-pinning.

@michaelblyons
Copy link
Contributor
michaelblyons commented May 5, 2025 •
edited
Loading

With the merges of #1511 and #1523, should this be closed?

Or is this issue to rebuild the book using those as the normal procedure? If so, isn't it a straight duplicate of #1529 and #1524?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@max123kl @michaelblyons @SetTrend @HonkingGoose @bagasme
0