diff options
| author | Jim Meyering <meyering@fb.com> | 2023-02-04 21:37:43 -0800 |
|---|---|---|
| committer | Jim Meyering <meyering@meta.com> | 2023-02-04 22:33:14 -0800 |
| commit | f3f7e21274d1f6962b2ce721b66d11e43521d0fd (patch) | |
| tree | e0deff3501f366e4972dc073aed3cdb7374ead63 /HACKING | |
| parent | fab6358d5a4f1ecd3660ba1da702156a59e5a263 (diff) | |
| download | grep-f3f7e21274d1f6962b2ce721b66d11e43521d0fd.tar.gz | |
maint: prefer https: to git:
The idea is to defend against some adversary-in-the-middle attacks.
Also prefer git.savannah.gnu.org over its shorter alias, git.sv.gnu.org
to avoid a warning e.g., from git clone.
Also, drop any final ".git" suffix on the resulting URIs.
Inspired by Paul Eggert's nearly identical changes to coreutils.
Induced by running these commands:
git grep -l 'git clone git:'|xargs perl -pi -e \
's{(git clone) git://(\S+)/([^/]+)\b}{$1 https://$2/git/$3}'
git grep -l git.sv.gn \
|xargs perl -pi -e 's{git\.sv\.gnu}{git\.savannah\.gnu}'
perl -pi -e \
's{(url =) git://(\S+)/([^/.]+)(\.git)?\b}{$1 https://$2/git/$3}'\
.gitmodules
* .gitmodules: As above.
* HACKING: Likewise.
* README-hacking: Likewise.
* src/grep.c (main): Likewise.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -12,7 +12,7 @@ Use the latest upstream sources Base any changes you make on the latest upstream sources. You can get a copy of the latest with this command: - git clone git://git.sv.gnu.org/grep + git clone https://git.savannah.gnu.org/git/grep That downloads the entire repository, including revision control history. Once downloaded, you can get incremental updates by running one of @@ -83,7 +83,7 @@ Make your changes on a private "topic" branch ============================================= So you checked out grep like this: - git clone git://git.sv.gnu.org/grep + git clone https://git.savannah.gnu.org/git/grep Now, cd into the grep/ directory and run: |