Re: [PATCH v3] refs.c: add a function to append a reflog entry to a fd
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Nov 20, 2014, 21:20 UTC
- Message-ID
- <20141120212022.GJ6527@google.com>
- In-Reply-To
- <1416508657-9057-1-git-send-email-sbeller@google.com>
Stefan Beller wrote:
Show 11 quoted lines
> From: Ronnie Sahlberg <sahlberg@google.com> > > Move code to create the string for a ref and write it to a file descriptor > from log_ref_write and add it into a new dedicated function > log_ref_write_fd. > > For now the new function is only used from log_ref_write, but later > on we will call this function from reflog transactions too. That means > that we will end up with only a single place, where we write a > reflog entry to a file instead of the current two places > (log_ref_write and builtin/reflog.c).
Line-wrapping width is still inconsistent. I don't think it's worth resending just for that, but something to look out for in the future.
> Signed-off-by: Ronnie Sahlberg <sahlberg@google.com> > Signed-off-by: Stefan Beller <sbeller@google.com>
[...]
> +++ b/refs.c
[...]
> @@ -3010,19 +3032,9 @@ static int log_ref_write(const char *refname, const unsigned char *old_sha1,
[...]
> + result = log_ref_write_fd(logfd, old_sha1, new_sha1,
> + git_committer_info(0), msg);
> + if (result) {
> int save_errno = errno;I don't understand why the above writes to a temporary variable and checks it, never to read that temporary again.
I don't think that alone is a reason to block the patch, but it worries me in that the review comment seems to have been just lost.