From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@ppc970.osdl.org>
Cc: git@vger.kernel.org
Subject: [PATCH] leftover bits for git rename
Date: Fri, 29 Apr 2005 15:42:09 -0700 [thread overview]
Message-ID: <7voebx2oji.fsf@assigned-by-dhcp.cox.net> (raw)
commit 2d280e1c5e6fdcf5428e60219eae14a2c6629c51
parent aed7a5a9dab96d1a17be4fadf7685086047178cc
author Linus Torvalds <torvalds@ppc970.osdl.org> Fri Apr 29 15:02:43 2005
committer Linus Torvalds <torvalds@ppc970.osdl.org> Fri Apr 29 15:02:43 2005
Update the merge scripts for the big git rename.
Let's see what else I forgot..
Not that many, but here they are.
Signed-off-by: Junio C Hamano <junkio@cox.net>
----
git-merge-one-file-script | 6 +++---
git-prune-script | 2 +-
git-tag-script | 2 +-
cd /opt/packrat/playpen/public/in-place/git/git.linus/
jit-snap -v 0
# - [PATCH] Makefile: The big git command renaming fallout fix.
# + working tree
--- k/git-merge-one-file-script (mode:100755)
+++ l/git-merge-one-file-script (mode:100755)
@@ -9,7 +9,7 @@
#
#
# Handle some trivial cases.. The _really_ trivial cases have
-# been handled already by read-tree, but that one doesn't
+# been handled already by git-read-tree, but that one doesn't
# do any merges that migth change the tree layout
#
@@ -41,7 +41,7 @@ case "${1:-.}${2:-.}${3:-.}" in
#
".$2." | "..$3" )
echo "Adding $4 with perm $6$7"
- mv $(unpack-file "$2$3") $4
+ mv $(git-unpack-file "$2$3") $4
chmod "$6$7" $4
git-update-cache --add -- $4
exit 0
@@ -55,7 +55,7 @@ case "${1:-.}${2:-.}${3:-.}" in
exit 1
fi
echo "Adding $4 with perm $6"
- mv $(unpack-file "$2") $4
+ mv $(git-unpack-file "$2") $4
chmod "$6" $4
git-update-cache --add -- $4
exit 0;;
--- k/git-prune-script (mode:100755)
+++ l/git-prune-script (mode:100755)
@@ -1,2 +1,2 @@
#!/bin/sh
-fsck-cache --unreachable $(cat .git/HEAD ) | grep unreachable | cut -d' ' -f3 | sed 's:^\(..\):.git/objects/\1/:' | xargs rm
+git-fsck-cache --unreachable $(cat .git/HEAD ) | grep unreachable | cut -d' ' -f3 | sed 's:^\(..\):.git/objects/\1/:' | xargs rm
--- k/git-tag-script (mode:100755)
+++ l/git-tag-script (mode:100755)
@@ -1,6 +1,6 @@
#!/bin/sh
object=${2:-$(cat .git/HEAD)}
-type=$(cat-file -t $object) || exit 1
+type=$(git-cat-file -t $object) || exit 1
( echo -e "object $object\ntype $type\ntag $1\n"; cat ) > .tmp-tag
rm -f .tmp-tag.asc
gpg -bsa .tmp-tag && cat .tmp-tag.asc >> .tmp-tag
reply other threads:[~2005-04-29 22:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7voebx2oji.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@ppc970.osdl.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