unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Better names for Guix versions from git?
Date: Sun, 30 Dec 2018 00:52:08 +0100	[thread overview]
Message-ID: <20181230005208.4e159c02@alma-ubu> (raw)
In-Reply-To: <87h8ewhrrw.fsf@elephly.net>

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

On Sat, 29 Dec 2018 23:50:11 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:

> swedebugia <swedebugia@riseup.net> writes:
> 
> > "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de> skrev: (29
> > december 2018 12:53:04 CET)  
> >>On Thu, 27 Dec 2018 22:30:11 +0100
> >>Taylan Kammer <taylan.kammer@gmail.com> wrote:
> >>  
> >>> I like dates in "rolling release" version strings because they
> >>> immediately tell you how old/new the version is, but I can
> >>> certainly live with that format too. Definitely better than what
> >>> we have.  
> >>
> >>I also would prefer a string containing the date.
> >>
> >>Björn  
> >
> > +1. Maybe we could do both, first the date then the commits then
> > the hash?  
> 
> Including a date would require more effort, because this format is not
> supported by git, as far as I know.
> 
> Support for the output of “git describe” would likely be much easier
> to implement, but note that this might require missing features to be
> implemented in guile-git.

If that is easier to implement, sure.

Björn


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-12-30  0:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-25 19:49 Better names for Guix versions from git? Taylan Kammer
2018-12-25 21:45 ` swedebugia
2018-12-26 13:57   ` Gábor Boskovits
2018-12-30  2:48     ` Vagrant Cascadian
2018-12-31 12:45       ` Hartmut Goebel
2018-12-26 14:02   ` Marius Bakke
2018-12-27 21:30     ` Taylan Kammer
2018-12-29 11:53       ` Björn Höfling
2018-12-29 16:39         ` swedebugia
2018-12-29 22:50           ` Ricardo Wurmus
2018-12-29 23:52             ` Björn Höfling [this message]
2019-01-05 17:45     ` 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=20181230005208.4e159c02@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).