Re: patch vs. overwrite in bzr

[Óscar Fuentes]

Andreas Schwab <address@hidden> writes:

> Óscar Fuentes <address@hidden> writes:
>
>> On addition, when I switch branches from Emacs the relevant function is
>> advised for storing timestamps of the files of the current branch before
>> the switch and recover the timestamps of the new branch's files after
>> the switch, so no rebuild is triggered because some source file was
>> modified by the switch when the new branch already has an associated up
>> to date build.
>
> Whatfor?  git doesn't touch files that didn't change when checking out a
> different revision.

The point is to keep the timestamps of the files that did change:

1. while in branch A, build the project; build products go to build/A
   directory.

2. switch to branch B.

3. switch to branch A.

All the files that are different among those branches now have altered
timestamps, so `make' thinks the products on build/A are out of date,
when in fact they are not. The scheme I described avoids this situation.