Re: [PATCH 0/3] Fixing volatile HEAD in push.default = current
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 23, 2013, 14:49 UTC
- Message-ID
- <7vip29hhuj.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CALkWK0mfGWA3aBntQQU5fkCJDPx+MUOScvMRJjS+JzjNucFzPw@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> I would argue that there is something to "fix", but that fix involves > making the cp a purely atomic operation which is super-complicated, > and totally not worth it. Would you _not_ like the above example to > work?
No. I do not think I like the above example to "work", at all.
I know we live in the real world, and I do not want to see such serializing implementations of cp or rm that try to "fix", as it will interfere my everyday use where such a race does not matter.