Well, I got here on topic #2 on a google search for golang date sprintf, 
soooooo. Relevant, topical, easily found. 



> On Jul 23, 2019, at 9:38 PM, Dan Kortschak <d...@kortschak.io> 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 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 at 18:45 -0500, Robert Engels wrote:
>> Funny. Did you remember it or just pay close attention to these
>> things?
>> 
>>> On Jul 23, 2019, at 6:38 PM, Dan Kortschak <d...@kortschak.io>
>>> 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
>>>> 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 are logging in a tight loop.
>>>>> 
>>>>> Russ
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google
>>> Groups "golang-nuts" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to golang-nuts+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/golang-nuts/fa535c9348925f7d5fbc01c924e2569abd967eb9.camel%40kortschak.io
>>> .
>> 
>> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/C7CD3A9E-6173-4F7F-A018-883939FFE5D5%40gmail.com.

Reply via email to