From: Pavel Roskin <proski@gnu.org>
To: git <git@vger.kernel.org>
Subject: [PATCH] cg-init shouldn't create master branch when pulling
Date: Wed, 27 Apr 2005 17:33:37 -0400 [thread overview]
Message-ID: <1114637617.15385.10.camel@dv> (raw)
Hello!
>From what I see in the current cogito sources, ".git/refs/heads/master"
is never used once it's created by cg-init. I believe the "master"
branch is only useful when creating a new repository. Then it's the
only branch in the repository.
When pulling from a remote repository, the "origin" branch is created,
and it should be default. There is no need in having a separate
"master" branch unless the user decides to create it for local
development.
This patch changes cg-init so that the "master" branch is only created
when the remote URI is not specified.
Signed-off-by: Pavel Roskin <proski@gnu.org>
Index: cg-init
===================================================================
--- 8dc4ace046ad3545d48088e604012f95e34e24d3/cg-init (mode:100755 sha1:d249140002888742c46ecba5925cae7c8025ea93)
+++ uncommitted/cg-init (mode:100755)
@@ -14,17 +14,18 @@
init-db
mkdir .git/branches .git/refs .git/refs/heads .git/refs/tags
-touch .git/refs/heads/master
-ln -s refs/heads/master .git/HEAD
if [ "$uri" ]; then
echo "$uri" >.git/branches/origin
+ ln -s refs/heads/origin .git/HEAD
cg-pull origin || die "pull failed"
- cp .git/refs/heads/origin .git/refs/heads/master
read-tree $(tree-id)
checkout-cache -a
update-cache --refresh
echo "Cloned (origin $uri available as branch \"origin\")"
+else
+ touch .git/refs/heads/master
+ ln -s refs/heads/master .git/HEAD
fi
--
Regards,
Pavel Roskin
next reply other threads:[~2005-04-27 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 21:33 Pavel Roskin [this message]
2005-05-03 20:48 ` [PATCH] cg-init shouldn't create master branch when pulling Pavel Roskin
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=1114637617.15385.10.camel@dv \
--to=proski@gnu.org \
--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