From: Alex Riesen <fork0@users.sourceforge.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, junkio@cox.net
Subject: Re: [PATCH 1/4] git-init-db should error out with a message
Date: Wed, 26 Oct 2005 21:45:20 +0200 [thread overview]
Message-ID: <20051026194520.GC8030@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.63.0510260139000.30576@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin, Wed, Oct 26, 2005 01:39:24 +0200:
> When the HEAD symref could not be created, it is helpful for the user to
> know that.
>
Not just that. It would be interesting to give the user an option to
use the file references ("ref: refs/heads/master").
Something like that:
Add --no-symref (make init-db use file references)
---
cache.h | 1 +
init-db.c | 11 +++++++++--
refs.c | 7 ++++++-
3 files changed, 16 insertions(+), 3 deletions(-)
applies-to: dba443573167bb9b0023613428e6d1a69477fac6
097ca1bf9b21d19d425e8151986eb36f82cbeff3
diff --git a/cache.h b/cache.h
index d776016..e410ce2 100644
--- a/cache.h
+++ b/cache.h
@@ -239,6 +239,7 @@ extern char *sha1_to_hex(const unsigned
extern int read_ref(const char *filename, unsigned char *sha1);
extern const char *resolve_ref(const char *path, unsigned char *sha1, int);
extern int create_symref(const char *git_HEAD, const char *refs_heads_master);
+extern int create_file_symref(const char *git_HEAD, const char *refs_heads_master);
extern int validate_symref(const char *git_HEAD);
/* General helper functions */
diff --git a/init-db.c b/init-db.c
index aabc09f..2d2b705 100644
--- a/init-db.c
+++ b/init-db.c
@@ -161,6 +161,8 @@ static void copy_templates(const char *g
closedir(dir);
}
+static int try_symref = 1;
+
static void create_default_files(const char *git_dir,
char *template_path)
{
@@ -191,8 +193,11 @@ static void create_default_files(const c
*/
strcpy(path + len, "HEAD");
if (read_ref(path, sha1) < 0) {
- if (create_symref(path, "refs/heads/master") < 0)
- exit(1);
+ int err = 0;
+ if ( try_symref )
+ err = create_symref(path, "refs/heads/master");
+ if ( !err && create_file_symref(path, "refs/heads/master") < 0 )
+ die("cannot create %s", path);
}
path[len] = 0;
copy_templates(path, len, template_path);
@@ -220,6 +225,8 @@ int main(int argc, char **argv)
break;
else if (!strncmp(arg, "--template=", 11))
template_dir = arg+11;
+ else if (!strcmp(arg, "--no-symref"))
+ try_symref = 0;
else
die(init_db_usage);
}
diff --git a/refs.c b/refs.c
index 97506a4..8029667 100644
--- a/refs.c
+++ b/refs.c
@@ -120,6 +120,12 @@ int create_symref(const char *git_HEAD,
unlink(git_HEAD);
return symlink(refs_heads_master, git_HEAD);
#else
+ return create_file_symref(git_HEAD, refs_heads_master);
+#endif
+}
+
+int create_file_symref(const char *git_HEAD, const char *refs_heads_master)
+{
const char *lockpath;
char ref[1000];
int fd, len, written;
@@ -144,7 +150,6 @@ int create_symref(const char *git_HEAD,
return -3;
}
return 0;
-#endif
}
int read_ref(const char *filename, unsigned char *sha1)
---
0.99.8.GIT
next prev parent reply other threads:[~2005-10-26 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 23:39 [PATCH 1/4] git-init-db should error out with a message Johannes Schindelin
2005-10-26 19:45 ` Alex Riesen [this message]
2005-10-26 20:27 ` Junio C Hamano
2005-10-26 20:47 ` Alex Riesen
2005-10-26 23:18 ` 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=20051026194520.GC8030@steel.home \
--to=fork0@users.sourceforge.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).