<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git, branch v1.5.6.5</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=v1.5.6.5</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=v1.5.6.5'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2008-08-06T20:40:53Z</updated>
<entry>
<title>GIT 1.5.6.5</title>
<updated>2008-08-06T20:40:53Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-08-06T19:04:06Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=781c1834f5419bdf81bb7f3750170ccd6b809174'/>
<id>urn:sha1:781c1834f5419bdf81bb7f3750170ccd6b809174</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Files given on the command line are relative to $cwd</title>
<updated>2008-08-06T20:38:18Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-08-06T18:43:47Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=dbd0f5c7692cce0c5fea535a06622b3a93df9598'/>
<id>urn:sha1:dbd0f5c7692cce0c5fea535a06622b3a93df9598</id>
<content type='text'>
When running "git commit -F file" and "git tag -F file" from a
subdirectory, we should take it as relative to the directory we started
from, not relative to the top-level directory.

This adds a helper function "parse_options_fix_filename()" to make it more
convenient to fix this class of issues.  Ideally, parse_options() should
support a new type of option, "OPT_FILENAME", to do this uniformly, but
this patch is meant to go to 'maint' to fix it minimally.

One thing to note is that value for "commit template file" that comes from
the command line is taken as relative to $cwd just like other parameters,
but when it comes from the configuration varilable 'commit.template', it
is taken as relative to the working tree root as before.  I think this
difference actually is sensible (not that I particularly think
commit.template itself is sensible).

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>fix diff-tree --stdin documentation</title>
<updated>2008-08-06T06:30:11Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-08-06T05:32:28Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=eabbc99a2198d1cae62ce951457e7edc23b5f1a9'/>
<id>urn:sha1:eabbc99a2198d1cae62ce951457e7edc23b5f1a9</id>
<content type='text'>
Long time ago, the feature of "diff-tree --stdin" to take a commit and its
parents on one line was broken, and did not support the common:

    git rev-list --parents $commits... -- $paths... |
    git diff-tree --stdin -v -p

usage pattern by Porcelains properly.  For diff-tree to talk sensibly
about commits, it needs to see commits, not just trees; the code was fixed
to take list of commits on the standard input in 1.2.0.

However we left the documentation stale for a long time, until Karl
Hasselström finally noticed it very recently.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>RelNotes 1.5.6.5 updates</title>
<updated>2008-08-06T04:20:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-08-06T04:20:59Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=2d0f5f3459278475602394a7165bf8919412f4e4'/>
<id>urn:sha1:2d0f5f3459278475602394a7165bf8919412f4e4</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>diff.renamelimit is a basic diff configuration</title>
<updated>2008-08-06T01:27:31Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2008-08-05T18:27:30Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=2b6ca6df2dbe9c23d0adfc1f59678a2d85c560b2'/>
<id>urn:sha1:2b6ca6df2dbe9c23d0adfc1f59678a2d85c560b2</id>
<content type='text'>
The configuration was added as a core option in 3299c6f (diff: make
default rename detection limit configurable., 2005-11-15), but 9ce392f
(Move diff.renamelimit out of default configuration., 2005-11-21)
separated diff-related stuff out of the core.

Up to that point it was Ok.

When we separated the Porcelain options out of the git_diff_config in
83ad63c (diff: do not use configuration magic at the core-level,
2006-07-08), we should have been more careful.

This mistake made diff-tree plumbing and git-show Porcelain to notice
different set of renames when the user explicitly asked for rename
detection.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-cvsimport.perl: Print "UNKNOWN LINE..." on stderr, not stdout.</title>
<updated>2008-08-05T18:40:28Z</updated>
<author>
<name>Jim Meyering</name>
<email>jim@meyering.net</email>
</author>
<published>2008-08-05T14:54:42Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=3be3999849bf993162fc957f47fc99325c324e9c'/>
<id>urn:sha1:3be3999849bf993162fc957f47fc99325c324e9c</id>
<content type='text'>
Signed-off-by: Jim Meyering &lt;meyering@redhat.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: typos / spelling fixes in older RelNotes</title>
<updated>2008-08-05T18:38:11Z</updated>
<author>
<name>Mike Ralphson</name>
<email>mike@abacus.co.uk</email>
</author>
<published>2008-08-05T16:12:06Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=f70f988b11f3ec24df023b105967978410828ea1'/>
<id>urn:sha1:f70f988b11f3ec24df023b105967978410828ea1</id>
<content type='text'>
Signed-off-by: Mike Ralphson &lt;mike@abacus.co.uk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-name-rev: don't use printf without format</title>
<updated>2008-08-03T19:48:41Z</updated>
<author>
<name>René Scharfe</name>
<email>rene.scharfe@lsrfire.ath.cx</email>
</author>
<published>2008-08-03T13:44:33Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=7c5b1675a88a52be1822129e4aa915c5531f6700'/>
<id>urn:sha1:7c5b1675a88a52be1822129e4aa915c5531f6700</id>
<content type='text'>
printf() without an explicit format string is not a good coding practise,
unless the printed string is guaranteed to not contain percent signs.  While
fixing this, we might as well combine the calls to fwrite() and printf().

Signed-off-by: Rene Scharfe &lt;rene.scharfe@lsrfire.ath.cx&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-name-rev: allow --name-only in combination with --stdin</title>
<updated>2008-08-02T18:07:50Z</updated>
<author>
<name>Pieter de Bie</name>
<email>pdebie@ai.rug.nl</email>
</author>
<published>2008-07-31T13:20:34Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=b003c00b7b5e352569061fec0b1e1bd0d0fa8b6a'/>
<id>urn:sha1:b003c00b7b5e352569061fec0b1e1bd0d0fa8b6a</id>
<content type='text'>
Signed-off-by: Pieter de Bie &lt;pdebie@ai.rug.nl&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>builtin-name-rev.c: split deeply nested part from the main function</title>
<updated>2008-08-02T18:04:22Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-08-02T18:04:22Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=e8b55fab6237b30494aa1905c3209d5bf5494a29'/>
<id>urn:sha1:e8b55fab6237b30494aa1905c3209d5bf5494a29</id>
<content type='text'>
The main function of this command implementation tries to do too many
things.  Split out a handling of single input line into a separate
function to reduce nesting level and clutter.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
