summaryrefslogtreecommitdiff
path: root/Documentation/mailmap.txt
diff options
context:
space:
mode:
authorLibravatar Jonathan Nieder <jrnieder@gmail.com>2011-01-02 21:05:46 -0600
committerLibravatar Jonathan Nieder <jrnieder@gmail.com>2011-02-26 04:59:37 -0600
commite832f43c1d26bf70611d98b62d95870a99292add (patch)
tree1b24a34f03268e1061ce6ee9c679c05b9912724b /Documentation/mailmap.txt
parentt0081 (line-buffer): add buffering tests (diff)
downloadtgif-e832f43c1d26bf70611d98b62d95870a99292add.tar.xz
vcs-svn: add binary-safe read function
buffer_read_string works well for non line-oriented input except for one problem: it does not tell the caller how many bytes were actually written. This means that unless one is very careful about checking for errors (and eof) the calling program cannot tell the difference between the string "foo" followed by an early end of file and the string "foo\0bar\0baz". So introduce a variant that reports the length, too, a thinner wrapper around strbuf_fread. Its result is written to a strbuf so the caller does not need to keep track of the number of bytes read. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Diffstat (limited to 'Documentation/mailmap.txt')
0 files changed, 0 insertions, 0 deletions