[libc++][doc] Add warning about limitation of --fresh in boostrapping build

[hawkinsw]

Add a warning to the Building Libcxx documentation about the limitations of the utility of --fresh at the top level.

[hawkinsw]

I hope that my lost time saves someone else!

cc @ldionne @EricWF (based on git-blame -- sorry if I inaccurately tagged!).

[ldionne]

LGTM with a small nitpick.

[ldionne]

@hawkinsw I have the option to squash and merge on your behalf here but it says the commit will be authored by [email protected]. I assume that's not what you want right (i.e. that's me misunderstanding how to use Github properly)?

[hawkinsw]

@hawkinsw I have the option to squash and merge on your behalf here but it says the commit will be authored by [email protected]. I assume that's not what you want right (i.e. that's me misunderstanding how to use Github properly)?

You are correct, that's not what I want. I am sorry that I obviously failed to understand how the new workflow works. I will attempt to figure it out and @ you when I have resolved it. I am sorry for all the pain for such a simple fix. I hope that the bigger change I am working on (implementing stride_view) will make up for it!

Thanks for your help!

[hawkinsw]

@ldionne I believe that I have fixed it now! You should see a drop-down that asks which email to associate with the commit. I would prefer [email protected]. Thank you for your patience!!

PS: In case you are wondering, the cause of this problem was that I had my verified email addresses set to hidden in my GitHub profile. As a result, GitHub was attempting to keep people from seeing my full address in public in the commit log. That is a nice feature, but the UI seems a little odd. I hope that information helps if you run into similar issues in the transition to GitHub workflows.

[ldionne]

Thanks for the explanation, this is good to know!