<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.comp.version-control.git">
    <title>gmane.comp.version-control.git</title>
    <link>http://blog.gmane.org/gmane.comp.version-control.git</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97743"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97742"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97741"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97740"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97739"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97738"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97737"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97736"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97735"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97734"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97733"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97732"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97731"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97730"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97729"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97728"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97727"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97726"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97725"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.git/97724"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97743">
    <title>Re: [PATCH] Implement git clone -v</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97743</link>
    <description>
Yes, it does. I'm not sure how to test it from the testsuite, maybe
redirect the output to a file and grep in it? It's ugly, that's why I
did not do so, but if you think a testcase is a musthave for this
feature then that's the way to go, I guess.
</description>
    <dc:creator>Miklos Vajna</dc:creator>
    <dc:date>2008-10-07T19:39:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97742">
    <title>[RFC] git rev-contains [Was: merge -s ffonly]</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97742</link>
    <description>Hello,

I already wrote similar tests and I wonder if this couldn't be done in a
new builtin command more effectively.  Something like

git rev-contains HEAD "$1"

.  I expect it to be faster and maybe it prevents a command line
overflow?!  (I remember something like 32000 chars max in a command, but
I could not trigger that with bash.)

Best regards
Uwe
</description>
    <dc:creator>Uwe Kleine-König</dc:creator>
    <dc:date>2008-10-07T18:58:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97741">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97741</link>
    <description>
Browsing git-config docs I would think that this variable is needed so
that git-config knows where to look for the git global configs file
that is under user $HOME directory, see the [FILES] section in git
config docs.

Thanks
Marco
</description>
    <dc:creator>Marco Costalba</dc:creator>
    <dc:date>2008-10-07T18:28:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97740">
    <title>Re: [PATCH] Fix a few typos in relnotes</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97740</link>
    <description>
Wow.  I really cannot type.  Thanks.  :-)

</description>
    <dc:creator>Shawn O. Pearce</dc:creator>
    <dc:date>2008-10-07T18:27:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97739">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97739</link>
    <description>
Right!


I see... but the only variable I have is HOMEPATH:

HOMEPATH=\Users\abdel

So I guess this was set by msysgit at installation time. But I see this 
variable only at the console (after typing 'set'), I don't see it in the 
user environment variable nor in the system one. So I guess the fix 
would be for msysgit to create this entry?

Thanks,
Abdel.

</description>
    <dc:creator>Abdelrazak Younes</dc:creator>
    <dc:date>2008-10-07T18:20:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97738">
    <title>[PATCH] Fix a few typos in relnotes</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97738</link>
    <description>---
  Documentation/RelNotes-1.6.0.3.txt |    8 ++++----
  1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/RelNotes-1.6.0.3.txt b/Documentation/RelNotes-1.6.0.3.txt
index edd5e45..6cf8ae4 100644
--- a/Documentation/RelNotes-1.6.0.3.txt
+++ b/Documentation/RelNotes-1.6.0.3.txt
&lt; at &gt;&lt; at &gt; -53,7 +53,7 &lt; at &gt;&lt; at &gt; Fixes since v1.6.0.2
  * Stale temporary files under $GIT_DIR/objects/pack are now cleaned up
    automatically by "git prune".

-* "git merge" once agrain removes directories after the last file has
+* "git merge" once again removes directories after the last file has
    been removed from it during the merge.

  * "git blame -C -C" no longer segfaults while trying to pass blame if
&lt; at &gt;&lt; at &gt; -68,10 +68,10 &lt; at &gt;&lt; at &gt; Fixes since v1.6.0.2
  * The "git commit" error message when there are still unmerged
    files present was clarified to match "git write-tree".

-* Some segfaults due to uncaught NULL pointers were fixed multiple
+* Some segfaults due to uncaught NULL pointers were fixed in multiple
    tools such as apply, reset, update-index.

-* Solaris bulds now default to OLD_ICONV=1 to avoid compile warnings.
+* Solaris builds now default to OLD_ICONV=1 to avoid compile warnings.

  * "Git.pm" tests relied on unnecessarily more recent version of Perl.

&lt; at &gt;&lt; at &gt; -80,7 +80,7 &lt; at &gt;&lt; at &gt; Fixes since v1.6.0.2
  * "gitweb" triggered undef warnings on missing trees.

  * "gitweb" now removes PATH_INFO from its URLs so users don't have
-  to manually set the url in the gitweb configuration.
+  to manually set the URL in the gitweb configuration.

  * Bash completion removed support for legacy "git-fetch", "git-push"
    and "git-pull" as these are no longer installed.  Dashless form
</description>
    <dc:creator>Mikael Magnusson</dc:creator>
    <dc:date>2008-10-07T18:15:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97737">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97737</link>
    <description>
Form git-config(1) docs:

This command will fail if:

-The config file is invalid,
......
-you use --global option without $HOME being properly set.


So please try to comment out following line

--- a/src/git.cpp
+++ b/src/git.cpp
&lt; at &gt;&lt; at &gt; -345,7 +345,7 &lt; at &gt;&lt; at &gt; void Git::userInfo(SList info) {
 info.clear();
 info &lt;&lt; "Environment" &lt;&lt; user &lt;&lt; email;

-errorReportingEnabled = false; // 'git config' could fail, see docs
+//errorReportingEnabled = false; // 'git config' could fail, see docs

 run("git config user.name", &amp;user);
 run("git config user.email", &amp;email);


run from double click and you probably will see an error message box
where git says $HOME is not set (I can reproduce this now).

So what I think is that when you run from command line there is the
$HOME variable set and command does not fails.


Marco
</description>
    <dc:creator>Marco Costalba</dc:creator>
    <dc:date>2008-10-07T18:03:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97736">
    <title>Re: [xfs-masters] git://oss.sgi.com broke</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97736</link>
    <description>

It seems OK now, thanks.
</description>
    <dc:creator>Andrew Morton</dc:creator>
    <dc:date>2008-10-07T17:39:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97735">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97735</link>
    <description>
So how do you explain this:

C:\&gt;git config --global user.name
Abdelrazak Younes

C:\&gt;git config user.name
Abdelrazak Younes

I get the same result in any directory, git repo or not.
FYI, I never set the name locally, just once and globally.

Abdel.


</description>
    <dc:creator>Abdelrazak Younes</dc:creator>
    <dc:date>2008-10-07T17:38:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97734">
    <title>Re: git://oss.sgi.com broke</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97734</link>
    <description>

Well I was kinda attached to the old format but my world wouldn't end
if it went away.

Judging from the Next/Trees contents, I suspect that Stephen uses the old
convenient/compact/one-per-file form too.

</description>
    <dc:creator>Andrew Morton</dc:creator>
    <dc:date>2008-10-07T17:32:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97733">
    <title>Re: Git and tagging hook</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97733</link>
    <description>
Why would they cull that other list, if the usual action is to "Reply
All" ?
</description>
    <dc:creator>Kristis Makris</dc:creator>
    <dc:date>2008-10-07T17:30:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97732">
    <title>Re: Git and tagging hook</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97732</link>
    <description>

If you are talking about taging locally, you can simply make an alias
or do something after tagging. Search archives for description when
it is worth to add a hook, and when it is not.

</description>
    <dc:creator>Jakub Narebski</dc:creator>
    <dc:date>2008-10-07T17:28:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97731">
    <title>Re: Git and tagging hook</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97731</link>
    <description>But the post-receive is NOT executed when I apply a tag.

I want the integration when I apply the tag to a local repository, NOT
only when I push/pull.

On Mon, 2008-10-06 at 09:17 +0200, Andreas Ericsson wrote:
</description>
    <dc:creator>Kristis Makris</dc:creator>
    <dc:date>2008-10-07T17:13:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97730">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97730</link>
    <description>
Yes, I know that but what is troublesome is that the user and email are 
not empty when git config is called outside of qgit.
What is even more troublesome is that the two calls to 'git config 
--global user.xxx' fail (but don't fail when called manually at the 
command line).

Abdel.

</description>
    <dc:creator>Abdelrazak Younes</dc:creator>
    <dc:date>2008-10-07T17:12:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97729">
    <title>Re: [QGit bug] git user settings not retrieved when launched for Windows explorer</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97729</link>
    <description>
OK.


No, as I said, 'git config user.name' is working just fine outside git 
directory.

Abdel.

</description>
    <dc:creator>Abdelrazak Younes</dc:creator>
    <dc:date>2008-10-07T17:08:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97728">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97728</link>
    <description>
Yes ! it is like this, I have finally had the possibility to test.

git config does not returns user and mail if run outside git dir
because user and mail are local set.
</description>
    <dc:creator>Marco Costalba</dc:creator>
    <dc:date>2008-10-07T16:55:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97727">
    <title>Re: [QGIT PATCH] Add safeguards to Git::userInfo()</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97727</link>
    <description>
An empty user and email it does not mean failure. Again, I would think
that is git config that returns no data (without failing) if it is run
from outside git directory.
</description>
    <dc:creator>Marco Costalba</dc:creator>
    <dc:date>2008-10-07T16:50:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97726">
    <title>Re: Repairing fatal: ref HEAD is not a symbolic ref (git checkout of svn remote)</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97726</link>
    <description>

Thanks, and the other svn remotes are working fine. I still have the
problem on the svn remote 'branches/1.2'. The following illustrates:

  (1.2_mybranch) $ git checkout 1.2
  Note: moving to "1.2" which isn't a local branch
  If you want to create a new branch from this checkout, you may do so
  (now or later) by using -b with the checkout command again. Example:
    git checkout -b &lt;new_branch_name&gt;
  HEAD is now at 76c7af2... Minor changes to CONTRIBUTORS

  (76c7af2...) $ git svn fetch
  MCONTRIBUTORS
  MLedgerSMB/AM.pm
  r2353 = ddd452af128f9b4698a1c1d6cc7fe2f23a0e6c90 (1.2)
  MLedgerSMB/AM.pm
  r2354 = fc6857004eeabf6963a9b2856f51db8842c00b70 (1.2)
  Segmentation fault

  (fc68570...) $ git checkout 1.2_print_pdf_default 
  Previous HEAD position was fc68570... (commit message snip)
  Switched to branch "1.2_print_pdf_default"

  (1.2_print_pdf_default) $ git svn rebase
  First, rewinding head to replay your work on top of it...
  Applying: naive replacement to option selected value="pdf" where PDF is format option,
  Segmentation fault

  (76c7af2...) $ git svn rebase
  fatal: ref HEAD is not a symbolic ref
  First, rewinding head to replay your work on top of it...
  Fast-forwarded HEAD to refs/remotes/1.2.
  Segmentation fault


This last git svn rebase on 'branches/1.2' (whether it's correct procedure
or not for a svn remote) used to work without the error until I issued
that one command (git checkout 4a3d99c0c9).

Thanks for any suggestions.

</description>
    <dc:creator>Jeff Kowalczyk</dc:creator>
    <dc:date>2008-10-07T16:49:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97725">
    <title>Re: [QGit bug] git user settings not retrieved when launched for Windows explorer</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97725</link>
    <description>
Hi Abdel,

I would think it is correct to return isErrorExit == false

The problem is that it seems git config return empty data if run from
outside git directory...isn't it ?


Marco
</description>
    <dc:creator>Marco Costalba</dc:creator>
    <dc:date>2008-10-07T16:48:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97724">
    <title>Re: [PATCH 0/4] diff text conversion filter</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97724</link>
    <description>Jeff King schrieb:

I think you are complicating things. We already have

   diff.doc.command ms-word-diff-script

and with your 4-patch-series-under-discussion we would have

   diff.doc.texconv antiword

and that should be sufficient. I'm proposing this heuristics:

 * If only textconv is given, all porcelains pick it.
 * If only command is given, all porcelains pick it.
 * If both are given, then
   - git log picks textconv.
   - git show and git diff:
     . if exactly one pathspec was given, pick command;
     . otherwise pick textconv

Plumbing never picks any of them, just like today, nor should git
format-patch. The are other porcelains that could be sorted into this
list, like git blame and (the summary line of) git commit.

BTW, please don't take git-gui as an example that would lauch MS-Word on
each diff. (Neither would gitk.) Both rely on plumbing, and that's good.
gitk has a menu entry "External diff", where the diff.doc.command could be
hooked into.

</description>
    <dc:creator>Johannes Sixt</dc:creator>
    <dc:date>2008-10-07T16:15:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.git/97723">
    <title>[PATCH] git rm: refresh index before up-to-date check</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.git/97723</link>
    <description>
Since "git rm" is supposed to be porcelain, we should convince it to
be user friendly by refreshing the index itself.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin&lt; at &gt;gmx.de&gt;
---
 builtin-rm.c  |    1 +
 t/t3600-rm.sh |   25 +++++++++++++++++--------
 2 files changed, 18 insertions(+), 8 deletions(-)

diff --git a/builtin-rm.c b/builtin-rm.c
index 50ae6d5..e06640c 100644
--- a/builtin-rm.c
+++ b/builtin-rm.c
&lt; at &gt;&lt; at &gt; -137,6 +137,7 &lt; at &gt;&lt; at &gt; int cmd_rm(int argc, const char **argv, const char *prefix)
 
 if (read_cache() &lt; 0)
 die("index file corrupt");
+refresh_cache(REFRESH_QUIET);
 
 pathspec = get_pathspec(prefix, argv);
 seen = NULL;
diff --git a/t/t3600-rm.sh b/t/t3600-rm.sh
index 558c80e..66aca99 100755
--- a/t/t3600-rm.sh
+++ b/t/t3600-rm.sh
&lt; at &gt;&lt; at &gt; -219,14 +219,23 &lt; at &gt;&lt; at &gt; test_expect_success 'Remove nonexistent file returns nonzero exit status' '
 
 test_expect_success 'Call "rm" from outside the work tree' '
 mkdir repo &amp;&amp;
-cd repo &amp;&amp;
-git init &amp;&amp;
-echo something &gt; somefile &amp;&amp;
-git add somefile &amp;&amp;
-git commit -m "add a file" &amp;&amp;
-(cd .. &amp;&amp;
- git --git-dir=repo/.git --work-tree=repo rm somefile) &amp;&amp;
-test_must_fail git ls-files --error-unmatch somefile
+(cd repo &amp;&amp;
+ git init &amp;&amp;
+ echo something &gt; somefile &amp;&amp;
+ git add somefile &amp;&amp;
+ git commit -m "add a file" &amp;&amp;
+ (cd .. &amp;&amp;
+  git --git-dir=repo/.git --work-tree=repo rm somefile) &amp;&amp;
+test_must_fail git ls-files --error-unmatch somefile)
+'
+
+test_expect_success 'refresh index before checking if it is up-to-date' '
+
+git reset --hard &amp;&amp;
+test-chmtime -86400 frotz/nitfol &amp;&amp;
+git rm frotz/nitfol &amp;&amp;
+test ! -f frotz/nitfol
+
 '
 
 test_done
</description>
    <dc:creator>Johannes Schindelin</dc:creator>
    <dc:date>2008-10-07T16:08:21</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.version-control.git">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.version-control.git</link>
  </textinput>
</rdf:RDF>
