Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] manual: cvs: document that a date can be used instead of a tag
Date: Mon, 20 Apr 2015 19:32:19 +0200	[thread overview]
Message-ID: <20150420173219.GA4057@free.fr> (raw)
In-Reply-To: <CAHkwnC-mOAdrGEt0E_FCrvf2kFZJ78UuWa+2h0a+Dco8dg49uA@mail.gmail.com>

Fabio, All,

On 2015-04-19 12:08 +0200, Fabio Porcedda spake thusly:
> On Sun, Apr 19, 2015 at 10:10 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2015-04-18 18:54 +0200, Fabio Porcedda spake thusly:
[--SNIP--]
> >> -     +LIBFOO_VERSION+ is 'mandatory' and 'must' be a timestamp.
> >> +     +LIBFOO_VERSION+ is 'mandatory' and 'must' be a tag or a date.
> >
> > I'd like we document the format of the date we recognise. Because, IIRC,
> > cvs accepts 'yesterday' as a date format, and that would be interpreted
> > as a tag with the current code.
> >
> > So maybe, just state something like:
> >
> >     ... or a date (YYYYMMDD:hhmmss)
> 
> What about this:
> (<YYYY>-<MM>-<DD>[T<HH><MM>[<SS>]] e.g 2015-12-20 or 2015-12-20T1010)

Well, this is exactly RFC3339;
    https://tools.ietf.org/html/rfc3339#section-5.8

So we may just state smehing along the lines of:

    ... or a date (formatted as defined in
    https://tools.ietf.org/html/rfc3339[RFC 3339]).

But I'd have to agree that it is not user-friendly, so we still want a
complete example, like so:

    ... or a date (formatted as defined in https://tools.ietf.org/html/rfc3339[RFC 3339],
    like <YYYY>-<MM>-<DD>[T<HH>:<MM>[:<SS>[.sss]]] e.g 2015-12-20 or 2015-12-20T10:10 or
    even 2015-12-20T16:42:12.467923; for complet ereference, see the
    http://sunsite.ualberta.ca/Documentation/Gnu/cvs-1.12.11/cvs.html#Date-input-formats[CVS
    manual]).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2015-04-20 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-18 16:54 [Buildroot] [PATCH 0/3] expect: bump to version 5.45.3 Fabio Porcedda
2015-04-18 16:54 ` [Buildroot] [PATCH 1/3] support/download/cvs: add support to use a date instead of a tag Fabio Porcedda
2015-04-19  8:04   ` Yann E. MORIN
2015-04-18 16:54 ` [Buildroot] [PATCH 2/3] manual: cvs: document that a date can be used " Fabio Porcedda
2015-04-19  8:10   ` Yann E. MORIN
2015-04-19 10:08     ` Fabio Porcedda
2015-04-19 15:45       ` Arnout Vandecappelle
2015-04-20  2:36         ` Fabio Porcedda
2015-04-20 21:06           ` Arnout Vandecappelle
2015-04-22  8:03             ` Fabio Porcedda
2015-04-22 16:29               ` Yann E. MORIN
2015-04-22 20:27                 ` Arnout Vandecappelle
2015-04-20 17:32       ` Yann E. MORIN [this message]
2015-04-18 16:54 ` [Buildroot] [PATCH 3/3] expect: bump to version 5.45.3 Fabio Porcedda
2015-04-19  8:11   ` Yann E. MORIN
2015-04-19 10:12     ` Fabio Porcedda
2015-04-19 10:35       ` Yann E. MORIN

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150420173219.GA4057@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox