mirror of
https://github.com/git/git.git
synced 2024-11-29 04:54:56 +08:00
d19938ab60
H. Peter Anvin mentioned that using SHA1_whatever as an
environment variable name is not nice and we should instead use
names starting with "GIT_" prefix to avoid conflicts. Here is
what this patch does:
* Renames the following environment variables:
New name Old Name
GIT_AUTHOR_DATE AUTHOR_DATE
GIT_AUTHOR_EMAIL AUTHOR_EMAIL
GIT_AUTHOR_NAME AUTHOR_NAME
GIT_COMMITTER_EMAIL COMMIT_AUTHOR_EMAIL
GIT_COMMITTER_NAME COMMIT_AUTHOR_NAME
GIT_ALTERNATE_OBJECT_DIRECTORIES SHA1_FILE_DIRECTORIES
GIT_OBJECT_DIRECTORY SHA1_FILE_DIRECTORY
* Introduces a compatibility macro, gitenv(), which does an
getenv() and if it fails calls gitenv_bc(), which in turn
picks up the value from old name while giving a warning about
using an old name.
* Changes all users of the environment variable to fetch
environment variable with the new name using gitenv().
* Updates the documentation and scripts shipped with Linus GIT
distribution.
The transition plan is as follows:
* We will keep the backward compatibility list used by gitenv()
for now, so the current scripts and user environments
continue to work as before. The users will get warnings when
they have old name but not new name in their environment to
the stderr.
* The Porcelain layers should start using new names. However,
just in case it ends up calling old Plumbing layer
implementation, they should also export old names, taking
values from the corresponding new names, during the
transition period.
* After a transition period, we would drop the compatibility
support and drop gitenv(). Revert the callers to directly
call getenv() but keep using the new names.
The last part is probably optional and the transition
duration needs to be set to a reasonable value.
Signed-off-by: Junio C Hamano <junkio@cox.net>
48 lines
1.0 KiB
C
48 lines
1.0 KiB
C
/*
|
|
* GIT - The information manager from hell
|
|
*
|
|
* Copyright (C) Linus Torvalds, 2005
|
|
*/
|
|
#include "cache.h"
|
|
|
|
void safe_create_dir(const char *dir)
|
|
{
|
|
if (mkdir(dir, 0755) < 0) {
|
|
if (errno != EEXIST) {
|
|
perror(dir);
|
|
exit(1);
|
|
}
|
|
}
|
|
}
|
|
|
|
/*
|
|
* If you want to, you can share the DB area with any number of branches.
|
|
* That has advantages: you can save space by sharing all the SHA1 objects.
|
|
* On the other hand, it might just make lookup slower and messier. You
|
|
* be the judge. The default case is to have one DB per managed directory.
|
|
*/
|
|
int main(int argc, char **argv)
|
|
{
|
|
const char *sha1_dir;
|
|
char *path;
|
|
int len, i;
|
|
|
|
safe_create_dir(".git");
|
|
|
|
sha1_dir = gitenv(DB_ENVIRONMENT);
|
|
if (!sha1_dir) {
|
|
sha1_dir = DEFAULT_DB_ENVIRONMENT;
|
|
fprintf(stderr, "defaulting to local storage area\n");
|
|
}
|
|
len = strlen(sha1_dir);
|
|
path = xmalloc(len + 40);
|
|
memcpy(path, sha1_dir, len);
|
|
|
|
safe_create_dir(sha1_dir);
|
|
for (i = 0; i < 256; i++) {
|
|
sprintf(path+len, "/%02x", i);
|
|
safe_create_dir(path);
|
|
}
|
|
return 0;
|
|
}
|