git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v3 01/14] refs.c make ref_transaction_create a wrapper to ref_transaction_update

From
Ronnie Sahlberg <sahlberg@google.com>
Date
Jun 18, 2014, 17:08 UTC
Message-ID
<1403111346-18466-2-git-send-email-sahlberg@google.com>
In-Reply-To
<1403111346-18466-1-git-send-email-sahlberg@google.com>
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
---
 refs.c | 13 ++-----------
 refs.h |  7 ++++---
 2 files changed, 6 insertions(+), 14 deletions(-)
diff --git a/refs.c b/refs.c
index dfbf003..a9f91ab 100644
--- a/refs.c
+++ b/refs.c
@@ -3487,23 +3487,14 @@ int ref_transaction_create(struct ref_transaction *transaction,
 			   int flags, const char *msg,
 			   struct strbuf *err)
 {
-	struct ref_update *update;
-
 	if (transaction->state != REF_TRANSACTION_OPEN)
 		die("BUG: create called for transaction that is not open");
 
 	if (!new_sha1 || is_null_sha1(new_sha1))
 		die("BUG: create ref with null new_sha1");
 
-	update = add_update(transaction, refname);
-
-	hashcpy(update->new_sha1, new_sha1);
-	hashclr(update->old_sha1);
-	update->flags = flags;
-	update->have_old = 1;
-	if (msg)
-		update->msg = xstrdup(msg);
-	return 0;
+	return ref_transaction_update(transaction, refname, new_sha1,
+				      null_sha1, flags, 1, msg, err);
 }
 
 int ref_transaction_delete(struct ref_transaction *transaction,
diff --git a/refs.h b/refs.h
index db463d0..495740d 100644
--- a/refs.h
+++ b/refs.h
@@ -283,9 +283,10 @@ struct ref_transaction *ref_transaction_begin(struct strbuf *err);
 /*
  * Add a reference update to transaction.  new_sha1 is the value that
  * the reference should have after the update, or zeros if it should
- * be deleted.  If have_old is true, then old_sha1 holds the value
- * that the reference should have had before the update, or zeros if
- * it must not have existed beforehand.
+ * be deleted.  If have_old is true and old_sha is not the null_sha1
+ * then the previous value of the ref must match or the update will fail.
+ * If have_old is true and old_sha1 is the null_sha1 then the ref must not
+ * already exist and a new ref will be created with new_sha1.
  * Function returns 0 on success and non-zero on failure. A failure to update
  * means that the transaction as a whole has failed and will need to be
  * rolled back.
-- 
2.0.0.467.g08c0633
Previous: Ronnie SahlbergNext: Junio C Hamano
Message 2 of 19 in “ref-transactions-reflog”
  1. 00/14 ref-transactions-reflogRonnie Sahlberg, Jun 18, 2014
  2. 01/14 refs.c make ref_transaction_create a wrapper to ref_transaction_updateRonnie Sahlberg, Jun 18, 2014
  3. Junio C HamanoJun 18, 2014
  4. 02/14 refs.c: make ref_transaction_delete a wrapper for ref_transaction_updateRonnie Sahlberg, Jun 18, 2014
  5. 03/14 refs.c: rename the transaction functionsRonnie Sahlberg, Jun 18, 2014
  6. 04/14 refs.c: add a new update_type field to ref_updateRonnie Sahlberg, Jun 18, 2014
  7. Junio C HamanoJun 18, 2014
  8. Re* [PATCH v3 04/14] refs.c: add a new update_type field to ref_updateJunio C Hamano, Jun 18, 2014
  9. Ronnie SahlbergJul 2, 2014
  10. 05/14 refs.c: add a function to append a reflog entry to a fdRonnie Sahlberg, Jun 18, 2014
  11. 06/14 lockfile.c: make hold_lock_file_for_append preserve meaningful errnoRonnie Sahlberg, Jun 18, 2014
  12. 07/14 refs.c: add a transaction function to append a reflog entryRonnie Sahlberg, Jun 18, 2014
  13. 08/14 refs.c: add a flag to allow reflog updates to truncate the logRonnie Sahlberg, Jun 18, 2014
  14. 09/14 refs.c: only write reflog update if msg is non-NULLRonnie Sahlberg, Jun 18, 2014
  15. 10/14 refs.c: allow multiple reflog updates during a single transactionRonnie Sahlberg, Jun 18, 2014
  16. 11/14 reflog.c: use a reflog transaction when writing during expireRonnie Sahlberg, Jun 18, 2014
  17. 12/14 refs.c: rename log_ref_setup to create_reflogRonnie Sahlberg, Jun 18, 2014
  18. 13/14 refs.c: make unlock_ref/close_ref/commit_ref staticRonnie Sahlberg, Jun 18, 2014
  19. 14/14 refs.c: remove lock_any_ref_for_updateRonnie Sahlberg, Jun 18, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.