From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: guix-devel@gnu.org
Subject: Re: Better names for Guix versions from git?
Date: Mon, 31 Dec 2018 13:45:06 +0100 [thread overview]
Message-ID: <d7e3aac9-657b-82b0-bd3e-3f873add60d7@goebel-consult.de> (raw)
In-Reply-To: <87sgyfrapz.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
Am 30.12.18 um 03:48 schrieb Vagrant Cascadian:
> The problem with dates from git commits is that git makes no attempt to
> keep commits in cronological order, and timezone adds interesting issues
> to the mix. For example:
Though *author* dates might not be in cronological order, *commit* dates
are (as long as none is playing with the graph), see below.
Anyway, we are interested in the *commit*-date, thus git need to be told
do show this one:
$ git log -n 1 --format=format:"%h %ci"
402c36c1d 2018-12-30 17:05:27 -0500
$git log -n 5 --format=format:"Author: %ai %an%nCommitter: %ci
%cn%n%n" c180017b6f7e9b6d23238c1fbaac986c435cd35e
Author: 2018-12-25 16:29:12 +0200 Efraim Flashner
Committer: 2018-12-27 14:55:54 +0200 Efraim Flashner
Author: 2018-11-20 17:46:24 +0100 Pierre-Antoine Rouby
Committer: 2018-12-27 12:08:25 +0100 Ludovic Courtès
Author: 2018-12-27 11:54:55 +0100 Ludovic Courtès
Committer: 2018-12-27 12:08:25 +0100 Ludovic Courtès
Author: 2018-12-27 11:53:14 +0100 Ludovic Courtès
Committer: 2018-12-27 12:08:25 +0100 Ludovic Courtès
Author: 2018-12-27 09:46:40 +0100 Julien Lepiller
Committer: 2018-12-27 09:47:22 +0100 Julien Lepiller
--
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development
Goebel Consult, Landshut
http://www.goebel-consult.de
Blog: https://www.goe-con.de/blog/35.000-gegen-vorratdatenspeicherung
Kolumne:
https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2010-09-mut-zur-beschraenkung
[-- Attachment #2: 0x7B752811BF773B65.asc --]
[-- Type: application/pgp-keys, Size: 16795 bytes --]
next prev parent reply other threads:[~2018-12-31 12:45 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 [this message]
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
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=d7e3aac9-657b-82b0-bd3e-3f873add60d7@goebel-consult.de \
--to=h.goebel@goebel-consult.de \
--cc=guix-devel@gnu.org \
/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).