unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 71371@debbugs.gnu.org, Josselin Poiret <dev@jpoiret.xyz>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	Mathieu Othacehe <othacehe@gnu.org>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	Florian Pelz <pelzflorian@pelzflorian.de>,
	Ricardo Wurmus <rekado@elephly.net>,
	Christopher Baines <guix@cbaines.net>,
	Matthew Trzcinski <matt@excalamus.com>
Subject: [bug#71371] [PATCH] gnu: svn-fetch: Make revision field optional.
Date: Wed, 05 Jun 2024 18:09:07 +0200	[thread overview]
Message-ID: <874ja774nw.fsf@gnu.org> (raw)
In-Reply-To: <d811c6461c7d653834c6a04290cacda5a72680b2.1717566375.git.mail@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 5 Jun 2024 07:52:02 +0200")

Hello!

Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:

> -@item @code{revision}
> -This string denotes revision to fetch specified as a number.
> +@item @code{revision} (default: @code{#f})
> +This field denotes the revision to fetch, as a number.  It can also be
> +set to @code{#f}, for example when @var{url} contains a tag reference.

Hmm, IIRC, tags in svn are mutable, no?

My recollection is that there’s no distinction between a directory, a
branch, and a tag: tags and branches are just a copy (‘svn cp’) of a
directory that can change over time.  Thus, you can’t rely on a tag as
an unambiguous reference.

Am I right?

Thanks,
Ludo’.




  reply	other threads:[~2024-06-05 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  5:52 [bug#71371] [PATCH] gnu: svn-fetch: Make revision field optional Nicolas Goaziou via Guix-patches via
2024-06-05 16:09 ` Ludovic Courtès [this message]
2024-06-05 20:44   ` Nicolas Goaziou via Guix-patches via
2024-06-05 16:32 ` Simon Tournier
2024-06-18  8:30 ` [bug#71371] [PATCH v2] gnu: svn-fetch: Allow specifying revisions as strings Nicolas Goaziou via Guix-patches via
2024-06-18 12:11   ` Maxim Cournoyer
2024-06-18 13:26     ` Nicolas Goaziou via Guix-patches via
2024-06-18 18:26       ` Maxim Cournoyer
2024-06-19  7:27         ` bug#71371: " Nicolas Goaziou via Guix-patches via
2024-06-25 15:19         ` [bug#71371] " Ludovic Courtès

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=874ja774nw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=71371@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=mail@nicolasgoaziou.fr \
    --cc=matt@excalamus.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    --cc=rekado@elephly.net \
    --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).