From patchwork Tue Apr 2 06:49:14 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: karthik nayak X-Patchwork-Id: 13613436 Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8E13F38DDD for ; Tue, 2 Apr 2024 06:49:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.51 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712040564; cv=none; b=JSM2VQWHkD5ciaf0t1N945Z68fC9yoZFU0UNSQ5FjoBuLxiPFIK12nNlPN/p4NEp+E5uvk+5N2OapMhfqtSmdljWG34urBiMxHrCf2HZIr4MB5/GJWjlAyGv/qknoqm1XdUWBzxoWLvVW2XocM0bAtfEAs6sYemzOKyKJhz+Syk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712040564; c=relaxed/simple; bh=Xl7PKSdw0Q5KjHyhVvm595HCHLJgvqm7A+VipYRRVbc=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=RURxqo9Q0OmRLanf7mf6YmP7dGdl8GfKFG7pMhSfFBYb3nGu4yfm5BeDnZYwBQHxoJC3yKsz71FXCKXxVoX3f3Yb6T7U3PSkLUOiHi1xU7byyiG1m49MzO4b5xl4TjQCuHGaiYH4G6bZaIhEjpVg2cKvDfQd9wIpmCxSZRIFeJE= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=CxBofkjL; arc=none smtp.client-ip=209.85.167.51 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="CxBofkjL" Received: by mail-lf1-f51.google.com with SMTP id 2adb3069b0e04-515a68d45faso5259181e87.3 for ; Mon, 01 Apr 2024 23:49:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712040561; x=1712645361; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=SnlZHsaVcL9W4hSL9oIM+l/KpP+j9+a8+PEjQ6j9g+A=; b=CxBofkjL+sZbdEF67nD/wVbRBOPJh804Xtdsa4fKfvtqYiQtB+/HZgMnTQvc7tC3le QlJv6mBVoTe5xd23JdwC+42oCs1w0KZx03GCy6QUv2UlGuddk2Hl2Dm+s6JDY4UlGv4X GgCzM6CxFwThBRNrAzgfo74ub0r4sfePsnzx3HbgXeeAavERQM43VZsnPcgVNBrn0Ip1 frZQq4YQrneQMsoDGQ4Z7vJRnMBq5zytDaVG+dQFVxxwkKqBBVagbydDIlNXh8PXrJAt mTAuu1jseV1KRpxbDebIr8eXS3jGp/xzZ6e1ItOSoA/sNM6qaj4R6XL7oAukyK2RzzvD +nUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712040561; x=1712645361; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=SnlZHsaVcL9W4hSL9oIM+l/KpP+j9+a8+PEjQ6j9g+A=; b=SVgQ/VAguHCPrEF30MsQzt8nDtooX8FuKSj7gPd9sN4aR6q8zedrMeVpKseg+LNoPA 9hMoODLedY6vHsuXkN/WXeQuWzbBzE3rXiXF8yue0QMHLKx07BrXC1iebfgQt/XCP1Ry oMyx/+hJWtBypvNCAi3uaTKd8TzHJvf4XBROUQhYIyO7HMmsRmmM/taBkmYgYDB901X1 ABP9Kbvy8lrqqBvjRhLcTCytiCszo7pBhiZszkAdQ1i+77Bfla4l4LGrDw/2tkwChoY6 chOXzbhUfgkpEsVL+ZT2xYXzBn0AJAqdu0+qdfaTZoebNuYPfZhANLE8IQRARtGXM2yI 5gKw== X-Forwarded-Encrypted: i=1; AJvYcCXpJl+bGKLx5MBDtylMybABsBRi4Tmv+/T5vzmkk/9esrq/QNbvGTbTC1ozYW8iqYIscwPhrkCGRjmkAF7MuHNWTML7 X-Gm-Message-State: AOJu0YypR2555v2NlEN6CAS2zmSr4jAxm5JuXKW/b47CHqWmNZ35ukVs uCWRKBVozofJ7q599vl7K/IpreaX1ljvjQanD/6Met5D9G0EQmhU X-Google-Smtp-Source: AGHT+IH3CkYBtGApabUhTuCwrHEnCJkDmnaqWJbZ7n2uCmqRLAOALcqU1vUEfUZ3sQfr7a1eOCgRzg== X-Received: by 2002:a05:6512:4c1:b0:515:d4fb:907f with SMTP id w1-20020a05651204c100b00515d4fb907fmr6057777lfq.27.1712040560304; Mon, 01 Apr 2024 23:49:20 -0700 (PDT) Received: from laptop.fritz.box ([2a02:2455:826e:4900:c3e0:2f8a:1ead:1494]) by smtp.gmail.com with ESMTPSA id n7-20020a509347000000b0056c24df7a78sm6582774eda.5.2024.04.01.23.49.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 01 Apr 2024 23:49:19 -0700 (PDT) From: Karthik Nayak X-Google-Original-From: Karthik Nayak To: karthik.188@gmail.com Cc: chris.torek@gmail.com, git@vger.kernel.org, gitster@pobox.com Subject: [PATCH v2 1/2] update-ref: use {old,new}-oid instead of {old,new}value Date: Tue, 2 Apr 2024 08:49:14 +0200 Message-ID: <20240402064915.191104-2-knayak@gitlab.com> X-Mailer: git-send-email 2.44.0 In-Reply-To: <20240402064915.191104-1-knayak@gitlab.com> References: <20240401144542.88027-1-knayak@gitlab.com> <20240402064915.191104-1-knayak@gitlab.com> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: Karthik Nayak The `git-update-ref` command is used to modify references. The usage of {old,new}value in the documentation refers to the OIDs. This is fine since the command only works with regular references which hold OIDs. But if the command is updated to support symrefs, we'd also be dealing with {old,new}-refs. To improve clarity around what exactly {old,new}value mean, let's rename it to {old,new}-oid. Signed-off-by: Karthik Nayak --- Documentation/git-update-ref.txt | 58 ++++++++++++++++---------------- builtin/update-ref.c | 26 +++++++------- t/t1400-update-ref.sh | 34 +++++++++---------- 3 files changed, 59 insertions(+), 59 deletions(-) diff --git a/Documentation/git-update-ref.txt b/Documentation/git-update-ref.txt index 0561808cca..374a2ebd2b 100644 --- a/Documentation/git-update-ref.txt +++ b/Documentation/git-update-ref.txt @@ -8,21 +8,21 @@ git-update-ref - Update the object name stored in a ref safely SYNOPSIS -------- [verse] -'git update-ref' [-m ] [--no-deref] (-d [] | [--create-reflog] [] | --stdin [-z]) +'git update-ref' [-m ] [--no-deref] (-d [] | [--create-reflog] [] | --stdin [-z]) DESCRIPTION ----------- -Given two arguments, stores the in the , possibly +Given two arguments, stores the in the , possibly dereferencing the symbolic refs. E.g. `git update-ref HEAD -` updates the current branch head to the new object. +` updates the current branch head to the new object. -Given three arguments, stores the in the , +Given three arguments, stores the in the , possibly dereferencing the symbolic refs, after verifying that -the current value of the matches . -E.g. `git update-ref refs/heads/master ` -updates the master branch head to only if its current -value is . You can specify 40 "0" or an empty string -as to make sure that the ref you are creating does +the current value of the matches . +E.g. `git update-ref refs/heads/master ` +updates the master branch head to only if its current +value is . You can specify 40 "0" or an empty string +as to make sure that the ref you are creating does not exist. It also allows a "ref" file to be a symbolic pointer to another @@ -56,15 +56,15 @@ ref symlink to some other tree, if you have copied a whole archive by creating a symlink tree). With `-d` flag, it deletes the named after verifying it -still contains . +still contains . With `--stdin`, update-ref reads instructions from standard input and performs all modifications together. Specify commands of the form: - update SP SP [SP ] LF - create SP SP LF - delete SP [SP ] LF - verify SP [SP ] LF + update SP SP [SP ] LF + create SP SP LF + delete SP [SP ] LF + verify SP [SP ] LF option SP LF start LF prepare LF @@ -82,10 +82,10 @@ specify a missing value, omit the value and its preceding SP entirely. Alternatively, use `-z` to specify in NUL-terminated format, without quoting: - update SP NUL NUL [] NUL - create SP NUL NUL - delete SP NUL [] NUL - verify SP NUL [] NUL + update SP NUL NUL [] NUL + create SP NUL NUL + delete SP NUL [] NUL + verify SP NUL [] NUL option SP NUL start NUL prepare NUL @@ -100,22 +100,22 @@ recognizes as an object name. Commands in any other format or a repeated produce an error. Command meanings are: update:: - Set to after verifying , if given. - Specify a zero to ensure the ref does not exist - after the update and/or a zero to make sure the + Set to after verifying , if given. + Specify a zero to ensure the ref does not exist + after the update and/or a zero to make sure the ref does not exist before the update. create:: - Create with after verifying it does not - exist. The given may not be zero. + Create with after verifying it does not + exist. The given may not be zero. delete:: - Delete after verifying it exists with , if - given. If given, may not be zero. + Delete after verifying it exists with , if + given. If given, may not be zero. verify:: - Verify against but do not change it. If - is zero or missing, the ref must not exist. + Verify against but do not change it. If + is zero or missing, the ref must not exist. option:: Modify the behavior of the next command naming a . @@ -141,7 +141,7 @@ abort:: Abort the transaction, releasing all locks if the transaction is in prepared state. -If all s can be locked with matching s +If all s can be locked with matching s simultaneously, all modifications are performed. Otherwise, no modifications are performed. Note that while each individual is updated or deleted atomically, a concurrent reader may @@ -161,7 +161,7 @@ formatted as: Where "oldsha1" is the 40 character hexadecimal value previously stored in , "newsha1" is the 40 character hexadecimal value of - and "committer" is the committer's name, email address + and "committer" is the committer's name, email address and date in the standard Git committer ident format. Optionally with -m: diff --git a/builtin/update-ref.c b/builtin/update-ref.c index 61338a01ec..e46afbc46d 100644 --- a/builtin/update-ref.c +++ b/builtin/update-ref.c @@ -9,8 +9,8 @@ #include "repository.h" static const char * const git_update_ref_usage[] = { - N_("git update-ref [] -d []"), - N_("git update-ref [] []"), + N_("git update-ref [] -d []"), + N_("git update-ref [] []"), N_("git update-ref [] --stdin [-z]"), NULL }; @@ -77,14 +77,14 @@ static char *parse_refname(const char **next) } /* - * The value being parsed is (as opposed to ; the + * The value being parsed is (as opposed to ; the * difference affects which error messages are generated): */ #define PARSE_SHA1_OLD 0x01 /* * For backwards compatibility, accept an empty string for update's - * in binary mode to be equivalent to specifying zeros. + * in binary mode to be equivalent to specifying zeros. */ #define PARSE_SHA1_ALLOW_EMPTY 0x02 @@ -140,7 +140,7 @@ static int parse_next_oid(const char **next, const char *end, goto invalid; } else if (flags & PARSE_SHA1_ALLOW_EMPTY) { /* With -z, treat an empty value as all zeros: */ - warning("%s %s: missing , treating as zero", + warning("%s %s: missing , treating as zero", command, refname); oidclr(oid); } else { @@ -158,14 +158,14 @@ static int parse_next_oid(const char **next, const char *end, invalid: die(flags & PARSE_SHA1_OLD ? - "%s %s: invalid : %s" : - "%s %s: invalid : %s", + "%s %s: invalid : %s" : + "%s %s: invalid : %s", command, refname, arg.buf); eof: die(flags & PARSE_SHA1_OLD ? - "%s %s: unexpected end of input when reading " : - "%s %s: unexpected end of input when reading ", + "%s %s: unexpected end of input when reading " : + "%s %s: unexpected end of input when reading ", command, refname); } @@ -194,7 +194,7 @@ static void parse_cmd_update(struct ref_transaction *transaction, if (parse_next_oid(&next, end, &new_oid, "update", refname, PARSE_SHA1_ALLOW_EMPTY)) - die("update %s: missing ", refname); + die("update %s: missing ", refname); have_old = !parse_next_oid(&next, end, &old_oid, "update", refname, PARSE_SHA1_OLD); @@ -225,10 +225,10 @@ static void parse_cmd_create(struct ref_transaction *transaction, die("create: missing "); if (parse_next_oid(&next, end, &new_oid, "create", refname, 0)) - die("create %s: missing ", refname); + die("create %s: missing ", refname); if (is_null_oid(&new_oid)) - die("create %s: zero ", refname); + die("create %s: zero ", refname); if (*next != line_termination) die("create %s: extra input: %s", refname, next); @@ -260,7 +260,7 @@ static void parse_cmd_delete(struct ref_transaction *transaction, have_old = 0; } else { if (is_null_oid(&old_oid)) - die("delete %s: zero ", refname); + die("delete %s: zero ", refname); have_old = 1; } diff --git a/t/t1400-update-ref.sh b/t/t1400-update-ref.sh index 6ebc3ef945..ec3443cc87 100755 --- a/t/t1400-update-ref.sh +++ b/t/t1400-update-ref.sh @@ -622,7 +622,7 @@ test_expect_success 'stdin fails create with no ref' ' test_expect_success 'stdin fails create with no new value' ' echo "create $a" >stdin && test_must_fail git update-ref --stdin err && - grep "fatal: create $a: missing " err + grep "fatal: create $a: missing " err ' test_expect_success 'stdin fails create with too many arguments' ' @@ -640,7 +640,7 @@ test_expect_success 'stdin fails update with no ref' ' test_expect_success 'stdin fails update with no new value' ' echo "update $a" >stdin && test_must_fail git update-ref --stdin err && - grep "fatal: update $a: missing " err + grep "fatal: update $a: missing " err ' test_expect_success 'stdin fails update with too many arguments' ' @@ -765,21 +765,21 @@ test_expect_success 'stdin update ref fails with wrong old value' ' test_expect_success 'stdin update ref fails with bad old value' ' echo "update $c $m does-not-exist" >stdin && test_must_fail git update-ref --stdin err && - grep "fatal: update $c: invalid : does-not-exist" err && + grep "fatal: update $c: invalid : does-not-exist" err && test_must_fail git rev-parse --verify -q $c ' test_expect_success 'stdin create ref fails with bad new value' ' echo "create $c does-not-exist" >stdin && test_must_fail git update-ref --stdin err && - grep "fatal: create $c: invalid : does-not-exist" err && + grep "fatal: create $c: invalid : does-not-exist" err && test_must_fail git rev-parse --verify -q $c ' test_expect_success 'stdin create ref fails with zero new value' ' echo "create $c " >stdin && test_must_fail git update-ref --stdin err && - grep "fatal: create $c: zero " err && + grep "fatal: create $c: zero " err && test_must_fail git rev-parse --verify -q $c ' @@ -803,7 +803,7 @@ test_expect_success 'stdin delete ref fails with wrong old value' ' test_expect_success 'stdin delete ref fails with zero old value' ' echo "delete $a " >stdin && test_must_fail git update-ref --stdin err && - grep "fatal: delete $a: zero " err && + grep "fatal: delete $a: zero " err && git rev-parse $m >expect && git rev-parse $a >actual && test_cmp expect actual @@ -1027,7 +1027,7 @@ test_expect_success 'stdin -z fails create with no ref' ' test_expect_success 'stdin -z fails create with no new value' ' printf $F "create $a" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: create $a: unexpected end of input when reading " err + grep "fatal: create $a: unexpected end of input when reading " err ' test_expect_success 'stdin -z fails create with too many arguments' ' @@ -1045,27 +1045,27 @@ test_expect_success 'stdin -z fails update with no ref' ' test_expect_success 'stdin -z fails update with too few args' ' printf $F "update $a" "$m" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: update $a: unexpected end of input when reading " err + grep "fatal: update $a: unexpected end of input when reading " err ' test_expect_success 'stdin -z emits warning with empty new value' ' git update-ref $a $m && printf $F "update $a" "" "" >stdin && git update-ref -z --stdin err && - grep "warning: update $a: missing , treating as zero" err && + grep "warning: update $a: missing , treating as zero" err && test_must_fail git rev-parse --verify -q $a ' test_expect_success 'stdin -z fails update with no new value' ' printf $F "update $a" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: update $a: unexpected end of input when reading " err + grep "fatal: update $a: unexpected end of input when reading " err ' test_expect_success 'stdin -z fails update with no old value' ' printf $F "update $a" "$m" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: update $a: unexpected end of input when reading " err + grep "fatal: update $a: unexpected end of input when reading " err ' test_expect_success 'stdin -z fails update with too many arguments' ' @@ -1083,7 +1083,7 @@ test_expect_success 'stdin -z fails delete with no ref' ' test_expect_success 'stdin -z fails delete with no old value' ' printf $F "delete $a" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: delete $a: unexpected end of input when reading " err + grep "fatal: delete $a: unexpected end of input when reading " err ' test_expect_success 'stdin -z fails delete with too many arguments' ' @@ -1101,7 +1101,7 @@ test_expect_success 'stdin -z fails verify with too many arguments' ' test_expect_success 'stdin -z fails verify with no old value' ' printf $F "verify $a" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: verify $a: unexpected end of input when reading " err + grep "fatal: verify $a: unexpected end of input when reading " err ' test_expect_success 'stdin -z fails option with unknown name' ' @@ -1160,7 +1160,7 @@ test_expect_success 'stdin -z update ref fails with wrong old value' ' test_expect_success 'stdin -z update ref fails with bad old value' ' printf $F "update $c" "$m" "does-not-exist" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: update $c: invalid : does-not-exist" err && + grep "fatal: update $c: invalid : does-not-exist" err && test_must_fail git rev-parse --verify -q $c ' @@ -1178,14 +1178,14 @@ test_expect_success 'stdin -z create ref fails with bad new value' ' git update-ref -d "$c" && printf $F "create $c" "does-not-exist" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: create $c: invalid : does-not-exist" err && + grep "fatal: create $c: invalid : does-not-exist" err && test_must_fail git rev-parse --verify -q $c ' test_expect_success 'stdin -z create ref fails with empty new value' ' printf $F "create $c" "" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: create $c: missing " err && + grep "fatal: create $c: missing " err && test_must_fail git rev-parse --verify -q $c ' @@ -1209,7 +1209,7 @@ test_expect_success 'stdin -z delete ref fails with wrong old value' ' test_expect_success 'stdin -z delete ref fails with zero old value' ' printf $F "delete $a" "$Z" >stdin && test_must_fail git update-ref -z --stdin err && - grep "fatal: delete $a: zero " err && + grep "fatal: delete $a: zero " err && git rev-parse $m >expect && git rev-parse $a >actual && test_cmp expect actual From patchwork Tue Apr 2 06:49:15 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: karthik nayak X-Patchwork-Id: 13613435 Received: from mail-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B27EF38DE4 for ; Tue, 2 Apr 2024 06:49:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.208.52 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712040564; cv=none; b=Q2spfsbOaES8hHmGUHjqRwg72/IPnGPCc+ptIQooRYrU36v6lzZCA2EFCAjCMPVZmOj+pyzopJfzFC1LU9QqSvXye+3+WjBZKFPMSdQthU11AydCT8vRzyepVD+iMGJFenPaYraGRQJauqX95Irppy6dAwhmoZq5H0TiSkuYqSo= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712040564; c=relaxed/simple; bh=53vEoIpGL//F3Kpsdo4YaRhmKY17vMioQPw66ojePrk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=CbXtkyAComwdGLuqw/3HFoTk3lh/YiifxPGhzokH2NSeGsBTX3Mxmu5Adkrav5O5Iwx/GJXbGOFlqMnQACCvXOPZ/XQ0io8BWPcFX08A7PvcCY+wK7UWBs4lugKIvbw06zYOiiewFn4+PStX9wSeUsTMAAZDhUvPv1f9DSooUTE= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=RnfONFvh; arc=none smtp.client-ip=209.85.208.52 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="RnfONFvh" Received: by mail-ed1-f52.google.com with SMTP id 4fb4d7f45d1cf-56bf6591865so6856932a12.0 for ; Mon, 01 Apr 2024 23:49:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712040561; x=1712645361; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=dShN5lbVlcmIi5FTCG5ExaQwq40xl/azZIHKDfczko4=; b=RnfONFvhiuLjbdHTfBgDzub9YMb+Rp6S28OoGB3CeAcz4qunB5zd/FZwIQdwcIK+l6 IGpyFh/Ilmd086p72gMbDAR2AIg1IGdCZOQc2t6/FykSRrEDcU/h30J+tYiH286z3wiL jbEYUyZyrk1xxyxREUnVU3lq8BFA+Erx0bZhrQLjrbzl5fB/n6q/d+3UamTuvjNH0bVI Na7PQMeCzR9oefxH+ZG4S9ZqyYG++jbBUeiFdaFaq2+Q7N74NB7vnvQfbYpAFwTinZbf EzivNLjG477vOk+b6bn+XMXOQakPsO0ryA+i7QEbOD1g6gGPxFr+vw3wjbDOSrUrmvqR My/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712040561; x=1712645361; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=dShN5lbVlcmIi5FTCG5ExaQwq40xl/azZIHKDfczko4=; b=TCiYHvB3TURC5dJfhdSXWEzmd1Jl4EnL7i1V/53C6DrwVNxNJoqjTC48ThjPVsff/+ jhL1XhDpREXeJiuzH0AA0WPkWbgUBjbiOm9WElSsO67jgnVFeP94G6feG7edmGUQqpX7 bHiRI2NEXZzDaoj0dEUCEhsSWl4lr5zeeXqbgQE+r7htZUdGW1ACVLbsrNlcMQxfXvc3 DBM3vBE7CoqDyJljXlMnGxEauVihN4CITcbY0up9OQ25XsC+eq5QFPgYvPQ05hPoj/r1 /6V/F30hqWrzkMeyQrI5mRIQpacfzlVedszBKkkFLpChD1zKfbv5S+0zax1PD9UBb5Z/ YJyQ== X-Forwarded-Encrypted: i=1; AJvYcCU3c0Ate16qvyUNEInH5yLLsQfAdnHd3n3Hza9LXwcxyGn4qdgI+OClACl7ex3BENIpglUnp1IEgV1QBUwlPVIxJIQ4 X-Gm-Message-State: AOJu0Yxx7vBOEwQfH/ENTUCfPkx9Xy7txgGpIVnJXNj21gJlF0gEILzF tl4uuOFyqrVREYfVGM78wY30cIaXUOMxbBDR1vofxVwG+tEnNFCe X-Google-Smtp-Source: AGHT+IEnO7C69WHy86hKDlE9WUnKDoTxZN4SEAV+9jEi2aPXMNJNetwCXsuChuNl+nA/bNYj+2ttsQ== X-Received: by 2002:a50:935a:0:b0:568:d729:a41a with SMTP id n26-20020a50935a000000b00568d729a41amr7792471eda.9.1712040561085; Mon, 01 Apr 2024 23:49:21 -0700 (PDT) Received: from laptop.fritz.box ([2a02:2455:826e:4900:c3e0:2f8a:1ead:1494]) by smtp.gmail.com with ESMTPSA id n7-20020a509347000000b0056c24df7a78sm6582774eda.5.2024.04.01.23.49.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 01 Apr 2024 23:49:20 -0700 (PDT) From: Karthik Nayak X-Google-Original-From: Karthik Nayak To: karthik.188@gmail.com Cc: chris.torek@gmail.com, git@vger.kernel.org, gitster@pobox.com Subject: [PATCH v2 2/2] githooks: use {old,new}-oid instead of {old,new}-value Date: Tue, 2 Apr 2024 08:49:15 +0200 Message-ID: <20240402064915.191104-3-knayak@gitlab.com> X-Mailer: git-send-email 2.44.0 In-Reply-To: <20240402064915.191104-1-knayak@gitlab.com> References: <20240401144542.88027-1-knayak@gitlab.com> <20240402064915.191104-1-knayak@gitlab.com> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: Karthik Nayak Similar to the previous commit, rename {old,new}-value in the 'githooks' documentation to {old,new}-oid. This improves clarity and also ensures consistency within the document. Signed-off-by: Karthik Nayak --- Documentation/githooks.txt | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Documentation/githooks.txt b/Documentation/githooks.txt index 37f91d5b50..ee9b92c90d 100644 --- a/Documentation/githooks.txt +++ b/Documentation/githooks.txt @@ -275,12 +275,12 @@ This hook executes once for the receive operation. It takes no arguments, but for each ref to be updated it receives on standard input a line of the format: - SP SP LF + SP SP LF -where `` is the old object name stored in the ref, -`` is the new object name to be stored in the ref and +where `` is the old object name stored in the ref, +`` is the new object name to be stored in the ref and `` is the full name of the ref. -When creating a new ref, `` is the all-zeroes object name. +When creating a new ref, `` is the all-zeroes object name. If the hook exits with non-zero status, none of the refs will be updated. If the hook exits with zero, updating of individual refs can @@ -503,13 +503,13 @@ given reference transaction is in: For each reference update that was added to the transaction, the hook receives on standard input a line of the format: - SP SP LF + SP SP LF -where `` is the old object name passed into the reference -transaction, `` is the new object name to be stored in the +where `` is the old object name passed into the reference +transaction, `` is the new object name to be stored in the ref and `` is the full name of the ref. When force updating the reference regardless of its current value or when the reference is -to be created anew, `` is the all-zeroes object name. To +to be created anew, `` is the all-zeroes object name. To distinguish these cases, you can inspect the current value of `` via `git rev-parse`.