POV-Ray : Newsgroups : povray.off-topic : Nope, I STILL don't understand git branches : Re: Nope, I STILL don't understand git branches Server Time
27 Jan 2026 15:00:06 EST (-0500)
  Re: Nope, I STILL don't understand git branches  
From: Cousin Ricky
Date: 27 Jan 2026 08:53:40
Message: <6978c364$1@news.povray.org>
On 2026-01-26 18:44 (-4), Bill Pragnell wrote:
> Jim Henderson <nos### [at] nospamcom> wrote:
>> On Sat, 24 Jan 2026 23:56:33 -0400, Cousin Ricky wrote:
>>
>>> The files README.md, gemcuts.pov, and gemcuts_description.txt were
>>> modified while one branch was checked out, and the changes show in the
>>> other branch as well.
>>
>> Hmm.  I guess then we'd need to see what the status looks like from each
>> branch.  What you're seeing isn't consistent with my experience, at least.
> 
> I think that's what I would expect. If the changes don't have conflicts with any
> of the other branches then switching branches makes no difference, the changes
> will be left alone (unless there is a conflict, then git will warn you to commit
> your changes or lose them when switching branch). If you commit the changes to a
> branch, then you'll only see those changes on that branch - and now they won't
> be listed as changes by 'git status' any more.

This is exactly what I've seen since Sunday.

> An untracked file is just a big change after all.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.