All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Casey <casey@nrlssc.navy.mil>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 3/4] git-reflog: add option --updateref to write the last reflog sha1 into the ref
Date: Fri, 22 Feb 2008 13:04:12 -0600	[thread overview]
Message-ID: <47BF1CAC.5000009@nrlssc.navy.mil> (raw)
In-Reply-To: <1203706541-21719-2-git-send-email-casey@nrlssc.navy.mil>

Certain sanity checks on the reflog assume that the sha1 of the top reflog
entry will be equal to the sha1 stored in the ref.

When reflog entries are deleted, this assumption may not hold. This patch
adds a new option to git-reflog which causes the subcommands "expire" and
"delete" to update the ref with the sha1 of the top-most reflog entry.

Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
---


This sucks in close_ref() and commit_ref() from refs.c. The changes to
expire_reflog() implement some of what write_ref_sha1() does. I guess
a new function in refs.c could have been made which instead of a logmsg
takes an updated reflog filename, but that seemed too contrived. We're
already modifying the reflog directly anyway, so maybe it's ok to modify
the ref directly too.

-brandon


 builtin-reflog.c |   17 ++++++++++++++++-
 1 files changed, 16 insertions(+), 1 deletions(-)

diff --git a/builtin-reflog.c b/builtin-reflog.c
index f685d76..280e24e 100644
--- a/builtin-reflog.c
+++ b/builtin-reflog.c
@@ -15,7 +15,7 @@
 static const char reflog_expire_usage[] =
 "git-reflog (show|expire) [--verbose] [--dry-run] [--stale-fix] [--expire=<time>] [--expire-unreachable=<time>] [--all] <refs>...";
 static const char reflog_delete_usage[] =
-"git-reflog delete [--verbose] [--dry-run] [--rewrite] <refs>...";
+"git-reflog delete [--verbose] [--dry-run] [--rewrite] [--updateref] <refs>...";
 
 static unsigned long default_reflog_expire;
 static unsigned long default_reflog_expire_unreachable;
@@ -25,6 +25,7 @@ struct cmd_reflog_expire_cb {
 	int dry_run;
 	int stalefix;
 	int rewrite;
+	int updateref;
 	int verbose;
 	unsigned long expire_total;
 	unsigned long expire_unreachable;
@@ -292,10 +293,20 @@ static int expire_reflog(const char *ref, const unsigned char *sha1, int unused,
 			status |= error("%s: %s", strerror(errno),
 					newlog_path);
 			unlink(newlog_path);
+		} else if (cmd->updateref &&
+			(write_in_full(lock->lock_fd,
+				sha1_to_hex(cb.last_kept_sha1), 40) != 40 ||
+			 write_in_full(lock->lock_fd, "\n", 1) != 1 ||
+			 close_ref(lock) < 0)) {
+			status |= error("Couldn't write %s",
+				lock->lk->filename);
+			unlink(newlog_path);
 		} else if (rename(newlog_path, log_file)) {
 			status |= error("cannot rename %s to %s",
 					newlog_path, log_file);
 			unlink(newlog_path);
+		} else if (cmd->updateref && commit_ref(lock)) {
+			status |= error("Couldn't set %s", lock->ref_name);
 		}
 	}
 	free(newlog_path);
@@ -372,6 +383,8 @@ static int cmd_reflog_expire(int argc, const char **argv, const char *prefix)
 			cb.stalefix = 1;
 		else if (!strcmp(arg, "--rewrite"))
 			cb.rewrite = 1;
+		else if (!strcmp(arg, "--updateref"))
+			cb.updateref = 1;
 		else if (!strcmp(arg, "--all"))
 			do_all = 1;
 		else if (!strcmp(arg, "--verbose"))
@@ -443,6 +456,8 @@ static int cmd_reflog_delete(int argc, const char **argv, const char *prefix)
 			cb.dry_run = 1;
 		else if (!strcmp(arg, "--rewrite"))
 			cb.rewrite = 1;
+		else if (!strcmp(arg, "--updateref"))
+			cb.updateref = 1;
 		else if (!strcmp(arg, "--verbose"))
 			cb.verbose = 1;
 		else if (!strcmp(arg, "--")) {
-- 
1.5.4.2.267.g38ea

  parent reply	other threads:[~2008-02-22 19:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 10:59 What's cooking in git.git (topics) Junio C Hamano
2008-02-03 21:43 ` Johannes Schindelin
2008-02-05  9:37 ` Junio C Hamano
2008-02-05 10:24   ` Jakub Narebski
2008-02-06  9:31     ` Junio C Hamano
2008-02-07  2:03   ` Junio C Hamano
2008-02-07  5:05     ` Jeff King
2008-02-07  9:43       ` Lars Hjemli
2008-02-07 10:32     ` Jakub Narebski
2008-02-10 10:48     ` Junio C Hamano
2008-02-10 16:29       ` Jakub Narebski
2008-02-10 16:48         ` Johannes Schindelin
2008-02-10 22:09         ` Junio C Hamano
2008-02-10 22:09         ` Junio C Hamano
2008-02-12  7:24       ` Junio C Hamano
2008-02-12  9:57         ` reflog-delete, was " Johannes Schindelin
2008-02-17  3:59         ` Junio C Hamano
2008-02-17 12:41           ` Jeff King
2008-02-17 13:52           ` Jakub Narebski
2008-02-17 18:59             ` Junio C Hamano
2008-02-17 22:01               ` Jakub Narebski
2008-02-18  0:37                 ` Junio C Hamano
2008-02-18  1:05                   ` Jakub Narebski
2008-02-17 15:48           ` Matthias Kestenholz
2008-02-17 18:10             ` Junio C Hamano
2008-02-17 18:22               ` Jeff King
2008-02-17 20:28           ` [Announce] 'next' rewound and rebased Junio C Hamano
2008-02-21  4:16           ` What's cooking in git.git (topics) Junio C Hamano
2008-02-21 10:40             ` Johannes Schindelin
2008-02-21 16:47               ` Junio C Hamano
2008-02-22 18:47               ` Brandon Casey
2008-02-22 18:56                 ` [PATCH 1/4] git-reflog: add option --rewrite to update reflog entries while expiring Brandon Casey
2008-02-22 21:08                   ` [PATCH] reflog-delete: parse standard reflog options Brandon Casey
     [not found]                 ` <1203706541-21719-1-git-send-email-casey@nrlssc.navy.mil>
2008-02-22 18:57                   ` [PATCH 2/4] refs.c: make close_ref() and commit_ref() non-static Brandon Casey
     [not found]                   ` <1203706541-21719-2-git-send-email-casey@nrlssc.navy.mil>
2008-02-22 19:04                     ` Brandon Casey [this message]
     [not found]                     ` <1203706541-21719-3-git-send-email-casey@nrlssc.navy.mil>
2008-02-22 19:04                       ` [PATCH 4/4] git-stash: add new 'drop' subcommand Brandon Casey
2008-02-22 22:52                         ` [PATCH] git-stash: add new 'pop' subcommand Brandon Casey
2008-02-22 22:26                 ` What's cooking in git.git (topics) Junio C Hamano
2008-02-23  0:19                   ` Brandon Casey
2008-02-23  0:29                     ` Junio C Hamano
2008-02-23  0:51                     ` Junio C Hamano
2008-02-23  2:43                       ` Brandon Casey
2008-02-25  8:40             ` Junio C Hamano
2008-02-28  0:45               ` Junio C Hamano
2008-03-01 20:15                 ` Junio C Hamano
2008-03-02 14:02                   ` Shawn O. Pearce
2008-03-03  2:06                   ` Junio C Hamano
2008-03-06  5:49                     ` Junio C Hamano
2008-03-06 17:01                       ` Johannes Schindelin
2008-03-08  9:38                       ` Junio C Hamano

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=47BF1CAC.5000009@nrlssc.navy.mil \
    --to=casey@nrlssc.navy.mil \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.