From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] manual: cvs: document that a date can be used instead of a tag
Date: Sun, 19 Apr 2015 17:45:01 +0200 [thread overview]
Message-ID: <5533CD7D.1070605@mind.be> (raw)
In-Reply-To: <CAHkwnC-mOAdrGEt0E_FCrvf2kFZJ78UuWa+2h0a+Dco8dg49uA@mail.gmail.com>
On 19/04/15 12:08, Fabio Porcedda wrote:
> On Sun, Apr 19, 2015 at 10:10 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>> Fabio, All,
>>
>> On 2015-04-18 18:54 +0200, Fabio Porcedda spake thusly:
>>> Also instead of using the generic word "timestamp" use the word "tag".
>>>
>>> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
>>> ---
>>> docs/manual/adding-packages-generic.txt | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
>>> index 8cf6bb6..be754a2 100644
>>> --- a/docs/manual/adding-packages-generic.txt
>>> +++ b/docs/manual/adding-packages-generic.txt
>>> @@ -280,7 +280,7 @@ information is (assuming the package name is +libfoo+) :
>>> Only anonymous pserver mode is supported.
>>> +LIBFOO_SITE+ 'must' contain the source URL as well as the remote
>>> repository directory. The module is the package name.
>>> - +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)
Can a timezone be added to that? Playing with dates and times without timezone
is dangerous.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-19 15:45 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 [this message]
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
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=5533CD7D.1070605@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.