Software Development

#7: Post edited by

alx‭ · 2022-06-21T11:32:47Z (almost 3 years ago)
links

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
$ sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
$ cd /some/git/repo/
$ patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
$ patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git-am`(1) as always, with confidence.
---
~~Source:~~
~~<https://lore.kernel.org/git/[email protected]/T/>~~

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
$ sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
$ cd /some/git/repo/
$ patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
$ patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git-am`(1) as always, with confidence.
---
See also:
<https://lore.kernel.org/git/[email protected]/T/>
Source code:
<https://git.kernel.org/pub/scm/utils/patatt/patatt.git>

#6: Post edited by

alx‭ · 2022-06-17T14:34:42Z (almost 3 years ago)

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
$ sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
$ cd /some/git/repo/
$ patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
$ patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
~~Then you can `git am ...` as always, with confidence.~~
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
$ sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
$ cd /some/git/repo/
$ patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
$ patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git-am`(1) as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

#5: Post edited by

alx‭ · 2022-06-17T14:34:20Z (almost 3 years ago)

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
~~sudo apt-get install patatt~~
```
And then for each repo in which you want to sign patches, run:
```sh
~~cd /some/git/repo/~~
~~patatt install-hook~~
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
~~patatt validate /path/to/incoming.patch~~
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
$ sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
$ cd /some/git/repo/
$ patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
$ patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

#4: Post edited by

alx‭ · 2022-06-17T14:33:55Z (almost 3 years ago)

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
~~Then you're done. Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.~~
To validate a patch before appying it:
```sh
patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use `git-format-patch`(1) and `git-send-email`(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

#3: Post edited by

alx‭ · 2022-06-17T14:32:53Z (almost 3 years ago)

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Basically, run:
```sh
sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Install the tool:
```sh
sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

#2: Post edited by

alx‭ · 2022-06-17T14:32:14Z (almost 3 years ago)

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Basically, run:
```sh
sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
~~Then you can `git am ...` as always, with confidence.~~

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).
Basically, run:
```sh
sudo apt-get install patatt
```
And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```
If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:
```
[user]
name = Alejandro Colomar
email = [email protected]
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```
Then you're done. Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.
To validate a patch before appying it:
```sh
patatt validate /path/to/incoming.patch
```
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can `git am ...` as always, with confidence.
---
Source:
<https://lore.kernel.org/git/[email protected]/T/>

#1: Initial revision by

alx‭ · 2022-06-17T14:31:34Z (almost 3 years ago)

Copy Link

Raw

Markdown

It can't be done with `git-send-email`(1), but there's a tool that integrates with it, and is very simple to use: [`patatt`(1)](https://github.com/mricon/patatt).

Basically, run:

```sh
sudo apt-get install patatt
```

And then for each repo in which you want to sign patches, run:
```sh
cd /some/git/repo/
patatt install-hook
```

If you have a `gpg`(1) keyring, and `.gitconfig` knows about it:

```
[user]
	name = Alejandro Colomar
	email = [email protected]
	signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
```

Then you're done.  Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.

To validate a patch before appying it:

```sh
patatt validate /path/to/incoming.patch
```

If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents.  If there's no signature it will print nothing (and return 0).

Then you can `git am ...` as always, with confidence.

Communities

Post History