Re: [PATCH 3/6] refs.c: replace write_str_in_full by write_in_full

2015-01-21 Thread Jeff King
On Wed, Jan 21, 2015 at 03:44:36PM -0800, Stefan Beller wrote: > On Wed, Jan 21, 2015 at 3:38 PM, Jeff King wrote: > > On Wed, Jan 21, 2015 at 03:23:42PM -0800, Stefan Beller wrote: > > > >> There is another occurrence where we could have used write_str_in_full > >> (line 3107: write_in_full(lock

Re: [PATCH 3/6] refs.c: replace write_str_in_full by write_in_full

2015-01-21 Thread Stefan Beller
On Wed, Jan 21, 2015 at 3:38 PM, Jeff King wrote: > On Wed, Jan 21, 2015 at 03:23:42PM -0800, Stefan Beller wrote: > >> There is another occurrence where we could have used write_str_in_full >> (line 3107: write_in_full(lock->lk->fd, &term, 1)), so the current state >> is inconsistent. This replac

Re: [PATCH 3/6] refs.c: replace write_str_in_full by write_in_full

2015-01-21 Thread Jeff King
On Wed, Jan 21, 2015 at 03:23:42PM -0800, Stefan Beller wrote: > There is another occurrence where we could have used write_str_in_full > (line 3107: write_in_full(lock->lk->fd, &term, 1)), so the current state > is inconsistent. This replaces the only occurrence of write_str_in_full > by write_in

[PATCH 3/6] refs.c: replace write_str_in_full by write_in_full

2015-01-21 Thread Stefan Beller
There is another occurrence where we could have used write_str_in_full (line 3107: write_in_full(lock->lk->fd, &term, 1)), so the current state is inconsistent. This replaces the only occurrence of write_str_in_full by write_in_full, so we only need to wrap write_in_full in the next patch. No func