From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH 09/11] refs.c: only write reflog update if msg is non-NULL
Date: Wed, 4 Jun 2014 11:57:50 -0700 [thread overview]
Message-ID: <1401908272-7600-10-git-send-email-sahlberg@google.com> (raw)
In-Reply-To: <1401908272-7600-1-git-send-email-sahlberg@google.com>
When performing a reflog transaction update, only write to the reflog iff
msg is non-NULL. This can then be combined with REFLOG_TRUNCATE to perform
an update that only truncates but does not write.
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
---
refs.c | 5 +++--
refs.h | 1 +
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/refs.c b/refs.c
index f2619e1..8faf5c1 100644
--- a/refs.c
+++ b/refs.c
@@ -3736,8 +3736,9 @@ int transaction_commit(struct ref_transaction *transaction,
update->reflog_fd = -1;
continue;
}
- if (log_ref_write_fd(update->reflog_fd, update->old_sha1,
- update->new_sha1,
+ if (update->msg &&
+ log_ref_write_fd(update->reflog_fd,
+ update->old_sha1, update->new_sha1,
update->committer, update->msg)) {
error("Could write to reflog: %s. %s",
update->refname, strerror(errno));
diff --git a/refs.h b/refs.h
index 5748cde..1b6a055 100644
--- a/refs.h
+++ b/refs.h
@@ -321,6 +321,7 @@ int transaction_delete_sha1(struct ref_transaction *transaction,
/*
* Append a reflog entry for refname. If the REFLOG_TRUNCATE flag is set
* this update will first truncate the reflog before writing the entry.
+ * If msg is NULL no update will be written to the log.
*/
int transaction_update_reflog(struct ref_transaction *transaction,
const char *refname,
--
2.0.0.578.gb9e379f
next prev parent reply other threads:[~2014-06-04 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 18:57 [PATCH 00/11] Add transaction support for reflog Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 01/11] refs.c make ref_transaction_create a wrapper to ref_transaction_update Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 02/11] refs.c: make ref_transaction_delete a wrapper for ref_transaction_update Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 03/11] refs.c: rename the transaction functions Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 04/11] refs.c: add a new update_type field to ref_update Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 05/11] refs.c: add a function to append a reflog entry to a fd Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 06/11] lockfile.c: make hold_lock_file_for_append preserve meaningful errno Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 07/11] refs.c: add a transaction function to append a reflog entry Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 08/11] refs.c: add a flag to allow reflog updates to truncate the log Ronnie Sahlberg
2014-06-04 18:57 ` Ronnie Sahlberg [this message]
2014-06-04 18:57 ` [PATCH 10/11] refs.c: allow multiple reflog updates during a single transaction Ronnie Sahlberg
2014-06-04 18:57 ` [PATCH 11/11] reflog.c: use a reflog transaction when writing during expire Ronnie Sahlberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401908272-7600-10-git-send-email-sahlberg@google.com \
--to=sahlberg@google.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).