From: Marius Bakke <mbakke@fastmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, guix-devel@gnu.org
Subject: Re: 01/02: gnu: fmt: Use HTTPS and git-fetch.
Date: Fri, 06 Mar 2020 15:37:01 +0100 [thread overview]
Message-ID: <87o8t9lfci.fsf@devup.no> (raw)
In-Reply-To: <20200306091525.E8A1621163@vcs0.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
Hello Pierre,
guix-commits@gnu.org writes:
> ambrevar pushed a commit to branch master
> in repository guix.
>
> commit 744f445c920f60e9080f42866c802184a1503a80
> Author: Pierre Neidhardt <mail@ambrevar.xyz>
> AuthorDate: Thu Mar 5 10:34:21 2020 +0100
>
> gnu: fmt: Use HTTPS and git-fetch.
>
> * gnu/packages/pretty-print.scm (fmt)[source]: Use git-fetch.
> [home-page]: Use HTTPS.
Why change to git-fetch here, when upstream provides a zipball?
The unzip input can be removed now, I guess.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next parent reply other threads:[~2020-03-06 14:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200306091524.5044.11103@vcs0.savannah.gnu.org>
[not found] ` <20200306091525.E8A1621163@vcs0.savannah.gnu.org>
2020-03-06 14:37 ` Marius Bakke [this message]
2020-03-06 15:07 ` 01/02: gnu: fmt: Use HTTPS and git-fetch Pierre Neidhardt
2020-03-06 17:40 ` Marius Bakke
2020-03-07 7:46 ` Pierre Neidhardt
2020-03-07 11:37 ` Pierre Neidhardt
2020-03-11 14:39 ` Ludovic Courtès
2020-03-11 14:54 ` Pierre Neidhardt
2020-05-13 1:08 ` best practise between git-fetch vs url-fetch? zimoun
2020-05-13 8:24 ` Brice Waegeneire
2020-05-13 18:07 ` Tobias Geerinckx-Rice
2020-05-14 16:16 ` Jack Hill
2020-05-24 20:04 ` Josh Marshall
2020-05-24 20:30 ` Ludovic Courtès
2020-05-25 4:54 ` Jack Hill
2020-05-25 21:17 ` Ludovic Courtès
2020-05-26 2:05 ` Jack Hill
2020-05-13 17:13 ` Leo Famulari
2020-05-24 20:34 ` Ludovic Courtès
2020-05-26 11:41 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8t9lfci.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).