Axel, I was saying (at least *meaning*) that it was impolite *of me* not to
answer *your* exhaustive comments! The other way around. But I now see why
you got upset. It may read that way too! I read things over many times, did
spell checking, but I didn't see this coming! I will read the rest of
This will copy over, it won’t append to it correct?
Sent from my iPhone
> On May 2, 2021, at 4:17 PM, Amnon wrote:
>
> Aha.
> OK, is
> https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured#Unstructured.DeepCopyInto
> what you are looking for?
>
>> On Sunday, 2 May 2021 at 19:1
Aha.
OK,
is
https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured#Unstructured.DeepCopyInto
what you are looking for?
On Sunday, 2 May 2021 at 19:18:43 UTC+1 mmahmo...@gmail.com wrote:
>
> https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured#section-documentation
On Sun, May 2, 2021 at 9:23 PM Øyvind Teig wrote:
> *Axel*, it is impolite not to try to comment and discuss each and every
> point above.
I wasn't trying to be impolite. But I also won't go through your messages
sentence by sentence, trying to say something even if I have nothing to
say. Sorry
One more thing, if (by presumably faulty reasoning above) random select is
never done, would we need the two guards in the second select?
https://go2goplay.golang.org/p/EJ2J1sQXVEk
søndag 2. mai 2021 kl. 21:23:13 UTC+2 skrev Øyvind Teig:
> *Axel*, it is impolite not to try to comment and disc
*Axel*, it is impolite not to try to comment and discuss each and every
point above. I actually started to do exactly that when I discovered that
it all boils down to this (FWIW?):
I have tried to expand on Jan's code (
https://go2goplay.golang.org/p/7xDzP6Jvyl8), here:
https://go2goplay.golang
Great, thanks.
On Sunday, May 2, 2021 at 8:03:59 PM UTC+2 axel.wa...@googlemail.com wrote:
> You can put the "however" at the beginning of the sentence:
>
> "The errors package also includes a new Unwrap function […]. However, it
> is usually better to use errors.Is or errors.As, since these fu
https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured#section-documentation
I am looking for something like the following
func mergeObjects(obj1 *uns.Unstructured, obj2 *uns.Unstructured)
(*uns.Unstructred, error) {
}
Thanks
On Sunday, May 2, 2021 at 1:35:06 PM UTC-4 Amnon wrote
You can put the "however" at the beginning of the sentence:
"The errors package also includes a new Unwrap function […]. However, it is
usually better to use errors.Is or errors.As, since these functions will
examine the entire chain in a single call."
This is the intended meaning. I agree that i
Hi Everyone,
On https://blog.golang.org/go1.13-errors there's a sentence:
"*It is usually better to use errors.Is or errors.As, however, since these
functions will examine the entire chain in a single call.*"
This sentence sounds like it has more to it, or the word *however *is an
extra wor
I am not sure what you mean by an unstructured object.
So probably best if you show us the code where they are defined.
On Sunday, 2 May 2021 at 16:37:12 UTC+1 mmahmo...@gmail.com wrote:
> Hi All:
>
> I am using two unstructured objects to represent two different
> ConfigMaps, of the same every
On Wednesday, February 24, 2021 at 7:42:24 PM UTC-8 Bryan C. Mills wrote:
> That said, that kind of coordinated release is *really* unpleasant, so
> this is one of the motivating problems for https://golang.org/issue/36460
> (which I've been actively working on since basically the start of 2020)
Hi All:
I am using two unstructured objects to represent two different ConfigMaps,
of the same everything but different data, I am looking for a way/API to
merge both into one ConfigMap
I am looking for something like DeepAppend() or DeepMerge()
any suggestion or recommendation ?
Thanks,
Mo
13 matches
Mail list logo
