On Friday, March 4, 2022 at 9:49:49 AM UTC+1 Konstantin Khomoutov wrote:

> On Thu, Mar 03, 2022 at 11:12:08PM -0800, skybuck2000 wrote: 
>
> >> There's no such support built into Git (because this simply goes 
> >> perpendicular to its data model, where multiple versions are recorded 
> for 
> >> the same file (well, actually, they are recorded across the content of 
> all 
> >> the files in the project 
> [...] 
> > What I would like also is for these differences to be visible on 
> > github/commits. 
>
> This is not possible due to the reasons I have presented above. 
>
> You can commit the addition of file1.txt, then commit the addition of 
> file2.txt which contents is based on that of file1.txt, but this does not 
> mean 
> anything to Git: there are two different files. 


I was under the impression that GIT calculates a hash based on the contents 
and can somehow detect same content.

Now it appears this is not the case, so this is a bit weird.

I guess this only applies if the content is exactly the same, and only the 
filename changed, perhaps only then git can detect a "rename".

(I tried adding version1.txt and version2.txt and version3.txt each on 
their own commit, git was unable to detect that these are the same file and 
that these files evolved, this sucks and is a weakness in git, it stops 
people from transitioning from a "natural" / "manual" / "intuitive" 
versioning system towards git :( )
 

> Think of it this way: suppose 
> your project has 100k files (think of Linux, for instance), and in a 
> particular commit you change two of them - do you expect Git to show you a 
> set 
> of differences between each of these files and 99999 other files, totaling 
> 2×99999 differences? I hope not. 
>

I don't see how this has anything to do with my problem :)
 
Bye,
  Skybuck.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/36c9af5f-389c-420a-b0e2-ed429b5a893an%40googlegroups.com.

Reply via email to