<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/setup.c, branch v1.4.4.4</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.4.4.4</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.4.4.4'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2006-10-31T03:35:16Z</updated>
<entry>
<title>Move deny_non_fast_forwards handling completely into receive-pack.</title>
<updated>2006-10-31T03:35:16Z</updated>
<author>
<name>Shawn Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2006-10-30T22:35:18Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=6fb75bed5c4a6ce099a24e581ea327e9de3ab8b0'/>
<id>urn:sha1:6fb75bed5c4a6ce099a24e581ea327e9de3ab8b0</id>
<content type='text'>
The 'receive.denynonfastforwards' option has nothing to do with
the repository format version.  Since receive-pack already uses
git_config to initialize itself before executing any updates we
can use the normal configuration strategy and isolate the receive
specific variables away from the core variables.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>add receive.denyNonFastforwards config variable</title>
<updated>2006-09-20T23:15:45Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2006-09-20T23:07:54Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=11031d7e9f34f6a20ff4a4bd4fa3e5e3c0024a57'/>
<id>urn:sha1:11031d7e9f34f6a20ff4a4bd4fa3e5e3c0024a57</id>
<content type='text'>
If receive.denyNonFastforwards is set to true, git-receive-pack will deny
non fast-forwards, i.e. forced updates. Most notably, a push to a repository
which has that flag set will fail.

As a first user, 'git-init-db --shared' sets this flag, since in a shared
setup, you are most unlikely to want forced pushes to succeed.

Signed-off-by: Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Fix crash when GIT_DIR is invalid</title>
<updated>2006-08-04T18:30:19Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2006-08-04T15:46:19Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=3a3c3fc42a021f11aa8f35dc40cc69d4d4af7224'/>
<id>urn:sha1:3a3c3fc42a021f11aa8f35dc40cc69d4d4af7224</id>
<content type='text'>
We used to test if a pointer was NULL, and if it was, try to access it.

Signed-off-by: Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>setup_git_directory_gently: do not barf when GIT_DIR is given.</title>
<updated>2006-07-31T00:45:57Z</updated>
<author>
<name>Matthias Lederhofer</name>
<email>matled@gmx.net</email>
</author>
<published>2006-07-30T01:30:29Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=41e95f699088b14c6a949ec858499f98df4f34f6'/>
<id>urn:sha1:41e95f699088b14c6a949ec858499f98df4f34f6</id>
<content type='text'>
Earlier we barfed when GIT_DIR environment variable points at a
directory yet to be created, which made it impossible to use
configuration mechanism in "git-init-db".

Signed-off-by: Matthias Lederhofer &lt;matled@gmx.net&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>shared repository: optionally allow reading to "others".</title>
<updated>2006-06-10T08:31:31Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-06-10T06:09:49Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=94df2506edd76a886a1044376f8c99349b2f226e'/>
<id>urn:sha1:94df2506edd76a886a1044376f8c99349b2f226e</id>
<content type='text'>
This enhances core.sharedrepository to have additionally
specify that read and exec permissions to be given to others as
well.  It is useful when serving a repository via gitweb and
git-daemon that runs as a user outside the project group.

The configuration item can take the following values:

    [core]
	sharedrepository 	 ; the same as "group"
	sharedrepository = true  ; ditto
	sharedrepository = 1	 ; ditto
	sharedrepository = group ; allow rwx to group
	sharedrepository = all   ; allow rwx to group, allow rx to other
	sharedrepository = umask ; not shared - use umask

It also extends "git init-db" to take "--shared=all" and friends
from the command line.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>revision parsing: make "rev -- paths" checks stronger.</title>
<updated>2006-04-27T00:08:44Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-04-26T22:09:27Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=ea92f41ff92b2fef54c8da4abb03c8101160a034'/>
<id>urn:sha1:ea92f41ff92b2fef54c8da4abb03c8101160a034</id>
<content type='text'>
If you don't have a "--" marker, then:

 - all of the arguments we are going to assume are pathspecs
   must exist in the working tree.

 - none of the arguments we parsed as revisions could be
   interpreted as a filename.

so that there really isn't any possibility of confusion in case
somebody does have a revision that looks like a pathname too.

The former rule has been in effect; this implements the latter.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Fix filename verification when in a subdirectory</title>
<updated>2006-04-26T19:16:21Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@osdl.org</email>
</author>
<published>2006-04-26T17:15:54Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=e23d0b4a4a55cc07e133905f0e9526b3550dd61b'/>
<id>urn:sha1:e23d0b4a4a55cc07e133905f0e9526b3550dd61b</id>
<content type='text'>
When we are in a subdirectory of a git archive, we need to take the prefix
of that subdirectory into accoung when we verify filename arguments.

Noted by Matthias Lederhofer

This also uses the improved error reporting for all the other git commands
that use the revision parsing interfaces, not just git-rev-parse. Also, it
makes the error reporting for mixed filenames and argument flags clearer
(you cannot put flags after the start of the pathname list).

[jc: with fix to a trivial typo noticed by Timo Hirvonen]

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Introduce core.sharedrepository</title>
<updated>2005-12-24T08:21:10Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2005-12-22T22:13:56Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=457f06d68e427bbf4f1a921877441a622a05e5c4'/>
<id>urn:sha1:457f06d68e427bbf4f1a921877441a622a05e5c4</id>
<content type='text'>
If the config variable 'core.sharedrepository' is set, the directories

	$GIT_DIR/objects/
	$GIT_DIR/objects/??
	$GIT_DIR/objects/pack
	$GIT_DIR/refs
	$GIT_DIR/refs/heads
	$GIT_DIR/refs/heads/tags

are set group writable (and g+s, since the git group may be not the primary
group of all users).

Since all files are written as lock files first, and then moved to
their destination, they do not have to be group writable.  Indeed, if
this leads to problems you found a bug.

Note that -- as in my first attempt -- the config variable is set in the
function which checks the repository format. If this were done in
git_default_config instead, a lot of programs would need to be modified
to call git_config(git_default_config) first.

[jc: git variables should be in environment.c unless there is a
 compelling reason to do otherwise.]

Signed-off-by: Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jc/subdir'</title>
<updated>2005-11-30T19:09:33Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-11-30T19:09:33Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=9cac9d368934f68e75810df95211a6522d4d139e'/>
<id>urn:sha1:9cac9d368934f68e75810df95211a6522d4d139e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do not attempt to access literal dirname "GIT_OBJECT_DIRECTORY".</title>
<updated>2005-11-30T18:51:24Z</updated>
<author>
<name>Tommi Virtanen</name>
<email>tv@inoi.fi</email>
</author>
<published>2005-11-30T15:37:10Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=0738fc2192109f946c033b3b003cb10aace9554e'/>
<id>urn:sha1:0738fc2192109f946c033b3b003cb10aace9554e</id>
<content type='text'>
Dereference the environment variable before using it.

Signed-off-by: Tommi Virtanen &lt;tv@inoi.fi&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
</feed>
