Re: [PATCH] fetch-pack: make unexpected peek result non-fatal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Junio C Hamano <gitster@xxxxxxxxx> writes:
> We used to die unless READ_NORMAL was returned, so the code after
> packet_reader_peek() can rely on reader->line to be populated.  Now
> that code must handle cases where an earlier _peek() gave something
> other than READ_NORMAL and in such an error case reader->line points
> at NULL.  So any code that assumed reader->line was populated needs
> to be updated.
> 
> Makes sense.

Thanks for taking a look. Yes, that's correct.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux