unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Brice Waegeneire <brice@waegenei.re>
Cc: zimoun <zimon.toutoune@gmail.com>,
	Guix-devel <guix-devel-bounces+brice+lists=waegenei.re@gnu.org>,
	guix-devel@gnu.org
Subject: Re: best practise between git-fetch vs url-fetch?
Date: Wed, 13 May 2020 20:07:28 +0200	[thread overview]
Message-ID: <878shv3dzz.fsf@nckx> (raw)
In-Reply-To: <f6b5f65941bea2feaf99498127b3a92d@waegenei.re>

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

Les Guix,

Brice Waegeneire 写道:
> Git references being content-addressed is important

That's only tautologically true if we limit ourselves to using raw 
commit hashes instead of the more common (because far more 
practical) named tags.  I obviously don't think we should do that.

If we don't, I fail to see how our git-fetches are 
‘content-addressed’ in a way that url-fetches supposedly aren't. 
Git tags are even easier to modify in place than tarballs, not 
harder.

> --with-commit

Yes, this is niice.  ♥

For the sake of argument¹, though, so is --with-source=<actually 
released and supported upstream tarball dot tar>.

Somehow erasing that hard distinction is the real winning move.

Kind regards,

T G-R

[1]: Obligatory <https://xkcd.com/1432>.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-05-13 18:07 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   ` 01/02: gnu: fmt: Use HTTPS and git-fetch Marius Bakke
2020-03-06 15:07     ` 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 [this message]
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=878shv3dzz.fsf@nckx \
    --to=me@tobias.gr \
    --cc=brice@waegenei.re \
    --cc=guix-devel-bounces+brice+lists=waegenei.re@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).