On Tue, 27 Jan 2026 10:02:14 -0400, Cousin Ricky wrote:

> On 2026-01-26 02:00 (-4), Jim Henderson wrote:
>> On Mon, 26 Jan 2026 17:44:27 EST, Bill Pragnell wrote:
>>>
>>> An untracked file is just a big change after all.
>> 
>> But it looks like the file is tracked, so any changes to it made in one
>> branch shouldn't affect other branches, unless they're either not
>> tracked (which isn't the case) or in .gitignore (which would *probably*
>> require it to have been explicitly added in some way, and I expect CR
>> would know if he'd done that).
> 
> I'm sensing disagreement in what "tracked" means.  Jim is using
> "tracked" the way I've understood it, but Bill is describing the
> behavior I'm seeing from git.
> 
> But .gitignore is one aspect of git that has never given me any
> surprises.

Can you describe the workflow you're using, step by step - commands 
executed, and so on - in order to try to reproduce what you're seeing?


-- 
"I learned long ago, never to wrestle with a pig. You get dirty, and 
besides, the pig likes it." - George Bernard Shaw

Post a reply to this message