I'm offering advice about how to more effectively use the group. Feel
free to ignore it.
On Tue, 2019-07-23 at 23:39 -0400, Chris Hornberger wrote:
> Well, I got here on topic #2 on a google search for golang date
> sprintf, soo. Relevant, topical, easily found.
>
>
>
> > On Jul 23, 2019,
Well, I got here on topic #2 on a google search for golang date sprintf,
soo. Relevant, topical, easily found.
> On Jul 23, 2019, at 9:38 PM, Dan Kortschak wrote:
>
> I couldn't find the thread in my go-nuts box, so I looked for it on
> google groups.
>
> Chris, it may be relevant, but
On Tue, 23 Jul 2019 18:45:14 -0500
Robert Engels wrote:
> Funny. Did you remember it or just pay close attention to these things?
I personally did not remember nor I paid close attention, I just read it.
> >>> On Thursday, April 5, 2012 at 3:24:09 PM UTC-4, Russ Cox wrote:
> >>> April 5, 2
Dan is the only one in this thread who pays attention to the actual value
of the timestamp not just to its format :-)
--Leo
On Tuesday, July 23, 2019 at 7:45:37 PM UTC-4, Robert Engels wrote:
>
> Funny. Did you remember it or just pay close attention to these things?
>
> > On Jul 23, 2019, at 6
I couldn't find the thread in my go-nuts box, so I looked for it on
google groups.
Chris, it may be relevant, but the thread is stale and so the
conversation is unlikely to be productive, particularly if people don't
have the previous comments that led up to this reanimation.
On Tue, 2019-07-23 a
Funny. Did you remember it or just pay close attention to these things?
> On Jul 23, 2019, at 6:38 PM, Dan Kortschak wrote:
>
> This thread is 7 years old.
>
>> On Tue, 2019-07-23 at 12:03 -0700, chrishornber...@gmail.com wrote:
>> Sometimes projects have upstream requirements that you can't ch
2:03 PM
To: golang-nuts
Subject: Re: [go-nuts] time.Format vs. fmt.Sprintf
Sometimes projects have upstream requirements that you can't change, avoid, or redefine. Sometimes you don't have a choice in how or what data you're providing downstream to other consumers. On Thursday, April
Sometimes projects have upstream requirements that you can't change, avoid,
or redefine. Sometimes you don't have a choice in how or what data you're
providing downstream to other consumers.
On Thursday, April 5, 2012 at 3:24:09 PM UTC-4, Russ Cox wrote:
>
> Maybe you should look into why you
