From: Brad Roberts <braddr@puremagic.com>
To: git@vger.kernel.org
Subject: [patch] fork optional branch point normazilation
Date: Sun, 17 Apr 2005 05:04:16 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0504170451030.2625-100000@bellevue.puremagic.com> (raw)
(ok, author looks better, but committer doesn't obey the AUTHOR_ vars yet)
This might not be how you intended git fork to behave, but without doing
_something_ to protect the head parameter a bit, this is just asking for a
corrutped .git/HEAD file.
commit 76faec069dfeae59c3ce5faaad10bdcded0cc908
tree c291316b28eff4042c80850cd93445345a606835
parent 1cdbc0a19b8d9b68f1f42735e2f14f1289823a63
author Brad Roberts <braddr@puremagic.com> 1113738584 -0700
committer Brad Roberts,,, <braddr@gameboy2> 1113738584 -0700
gitfork needs to normalize the optional third parameter before using it.
Index: gitfork.sh
===================================================================
--- 51b1bddbbc05e50d5bbf1f9662e503c2e85d5e96/gitfork.sh (mode:100755 sha1:e5692ea9bdbc39b028fe1e1205381da632541bab)
+++ c291316b28eff4042c80850cd93445345a606835/gitfork.sh (mode:100755 sha1:386148ae9a99739d06a09742ff4157d0f7e4e223)
@@ -37,6 +37,7 @@
[ -e "$destdir" ] && die "$destdir already exists"
[ "$head" ] || head=$(commit-id)
+head=$(gitXnormid.sh -c $head)
git lntree "$destdir"
echo $head >.git/heads/$name
next reply other threads:[~2005-04-17 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 12:04 Brad Roberts [this message]
2005-04-17 12:25 ` fork optional branch point normazilation Petr Baudis
2005-04-17 12:40 ` Brad Roberts
2005-04-17 17:13 ` [patch] " Linus Torvalds
2005-04-17 17:21 ` Daniel Barkalow
2005-04-17 23:27 ` Brad Roberts
2005-04-17 23:39 ` Linus Torvalds
2005-04-18 0:23 ` Petr Baudis
2005-04-18 1:07 ` Linus Torvalds
2005-04-18 1:51 ` [PATCH] remove_special() tentative fix Junio C Hamano
2005-04-18 2:01 ` [patch] fork optional branch point normazilation Brad Roberts
2005-04-18 10:45 ` Martin Schlemmer
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=Pine.LNX.4.44.0504170451030.2625-100000@bellevue.puremagic.com \
--to=braddr@puremagic.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).