<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/git.c, branch v1.5.0.7</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.0.7</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.0.7'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2007-03-03T20:26:50Z</updated>
<entry>
<title>builtin-archive: use RUN_SETUP</title>
<updated>2007-03-03T20:26:50Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2007-03-03T16:14:25Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=64edf4b2eb19e5b94eda60c0e21d85e45602a8f1'/>
<id>urn:sha1:64edf4b2eb19e5b94eda60c0e21d85e45602a8f1</id>
<content type='text'>
It used to roll its own setup.

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>Allow aliases to expand to shell commands</title>
<updated>2007-02-11T06:46:34Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2007-02-11T00:33:58Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=dfd42a3c6281275b518f10938dcd858558cd82e3'/>
<id>urn:sha1:dfd42a3c6281275b518f10938dcd858558cd82e3</id>
<content type='text'>
If the alias expansion is prefixed with an exclamation point, treat
it as a shell command which is run using system(3).

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Print a sane error message if an alias expands to an invalid git command</title>
<updated>2007-02-11T06:46:30Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2007-02-11T00:33:57Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=f3dd015c9147e3116fc1941d96f4dad38386b1db'/>
<id>urn:sha1:f3dd015c9147e3116fc1941d96f4dad38386b1db</id>
<content type='text'>
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Commands requiring a work tree must not run in GIT_DIR</title>
<updated>2007-02-05T22:02:16Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2007-01-23T12:30:20Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=6d9ba67b0fc2f18c1d7a65514edbdcdf86429c1c'/>
<id>urn:sha1:6d9ba67b0fc2f18c1d7a65514edbdcdf86429c1c</id>
<content type='text'>
This patch helps when you accidentally run something like git-clean
in the git directory instead of the work tree.

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>Make fsck and fsck-objects be builtins.</title>
<updated>2007-01-29T17:36:21Z</updated>
<author>
<name>Mark Wooding</name>
<email>mdw@distorted.org.uk</email>
</author>
<published>2007-01-29T15:48:06Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=b4dfefe00f7035140b7a10e855a665c1347cacd6'/>
<id>urn:sha1:b4dfefe00f7035140b7a10e855a665c1347cacd6</id>
<content type='text'>
The earlier change df391b192 to rename fsck-objects to fsck broke
fsck-objects.  This should fix it again.

Signed-off-by: Mark Wooding &lt;mdw@distorted.org.uk&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Rename git-repo-config to git-config.</title>
<updated>2007-01-29T00:16:53Z</updated>
<author>
<name>Tom Prince</name>
<email>tom.prince@ualberta.net</email>
</author>
<published>2007-01-29T00:16:53Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=e0d10e1c63bc52b37bbec99b07deee794058d9b4'/>
<id>urn:sha1:e0d10e1c63bc52b37bbec99b07deee794058d9b4</id>
<content type='text'>
Signed-off-by: Tom Prince &lt;tom.prince@ualberta.net&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>git-blame --incremental: don't use pager</title>
<updated>2007-01-28T19:00:57Z</updated>
<author>
<name>Ren,Ai(B Scharfe</name>
<email>rene.scharfe@lsrfire.ath.cx</email>
</author>
<published>2007-01-28T14:25:55Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=4f0219a4c76a2ce963cf355f90f18c9c59036bca'/>
<id>urn:sha1:4f0219a4c76a2ce963cf355f90f18c9c59036bca</id>
<content type='text'>
Starting a pager defeats the purpose of the incremental output
mode.  This changes git-blame to only paginate if --incremental
was not given.

git -p blame --incremental still starts the pager, though.

Signed-off-by: Rene Scharfe &lt;rene.scharfe@lsrfire.ath.cx&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>annotate: use pager</title>
<updated>2007-01-24T23:08:31Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>Johannes.Schindelin@gmx.de</email>
</author>
<published>2007-01-24T14:04:37Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=e955ae957c401cb541f23d46af66c9b3d5b8ffe9'/>
<id>urn:sha1:e955ae957c401cb541f23d46af66c9b3d5b8ffe9</id>
<content type='text'>
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/bare'</title>
<updated>2007-01-12T00:50:36Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2007-01-12T00:50:36Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=e861ce1692fa9809f3e7b898804f8ddaf7cd8975'/>
<id>urn:sha1:e861ce1692fa9809f3e7b898804f8ddaf7cd8975</id>
<content type='text'>
* jc/bare:
  Disallow working directory commands in a bare repository.
  git-fetch: allow updating the current branch in a bare repository.
  Introduce is_bare_repository() and core.bare configuration variable
  Move initialization of log_all_ref_updates
</content>
</entry>
<entry>
<title>Disallow working directory commands in a bare repository.</title>
<updated>2007-01-10T23:03:09Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2006-12-31T04:32:38Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=7eff28a9b42cb0d3aad932338b2e645fc6ed8fa9'/>
<id>urn:sha1:7eff28a9b42cb0d3aad932338b2e645fc6ed8fa9</id>
<content type='text'>
If the user tries to run a porcelainish command which requires
a working directory in a bare repository they may get unexpected
results which are difficult to predict and may differ from command
to command.

Instead we should detect that the current repository is a bare
repository and refuse to run the command there, as there is no
working directory associated with it.

[jc: updated Shawn's original somewhat -- bugs are mine.]

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
</feed>
