On Mon, Mar 6, 2023 at 8:41 AM Uwe Brauer wrote:
>
>
> > On Sat, Mar 4, 2023 at 1:39 AM Uwe Brauer wrote:
>
> > It's calculated on the fly.
>
> Ok, that I was afraid of.
>
> > Weirdly enough, I wrote a blog post [1] about a debate in 2012
> > precisely about the differences between git and mercur
Hi Konstantin,
Thank you so much for your answer! It's really clear now.
Have a nice day,
Sarah
Le mer. 1 mars 2023 à 17:34, Konstantin Khomoutov a
écrit :
> On Wed, Mar 01, 2023 at 01:45:08AM -0800, 'Sarah GOMEY' via Git for human
> beings wrote:
>
> Disclaimer (which might get a bit more obv
Last try
>>> "UB" == Uwe Brauer writes:
>> On Sat, Mar 4, 2023 at 1:39 AM Uwe Brauer wrote:
>> It's calculated on the fly.
Ok, that I was afraid of.
> Weirdly enough, I wrote a blog post [1] about a debate in 2012
> precisely about the differences between git and mercurial, and how
> `git
>>> "PO" == Philip Oakley writes:
Hi Philip,
> Hi Uwe,
> (supplemental to Felipe's reply)
I hope this message goes to the mailing list, I answered Felipe's mail
and again the message to the mailing list was rejected. That happened to
Tassilo some time ago. Sigh.
> Underlying the 'branch name
Hi Uwe,
(supplemental to Felipe's reply)
Underlying the 'branch name' "problem" is the same conceptual shift that
Git adopts for the separation of file names from the (blob) content.
By separating the metadata from the item, Git allows itself to pivot from
being human centric (with all our inse
