git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Levedahl <mlevedahl@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: rc4 - make quick-install-doc is broken
Date: Sat, 04 Aug 2007 13:56:31 -0400	[thread overview]
Message-ID: <46B4BDCF.9060809@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708041719490.14781@racer.site>

Johannes Schindelin wrote:
> At this point, could you try debugging it?  For example, set a break point 
> in set_work_tree(), since that is the only function that commit touches, 
> and see what it returns both before and after the bad commit?
>
> Ciao,
> Dscho
>
>
>   
Before the bad commit, set_work_tree returns (null), and
variable dir_buffer in the call to get_relative_cwd is 
"/usr/src/git/.git/HEAD"

After, it returns "Documentation/", and
variable dir_buffer in the call to get_relative_cwd is "/usr/src/git"

I do not understand what the desired changes in this patch were so am 
really lost as to what should be fixed. However, the above I hope will 
give you a good clue as to what is broken.

Mark

  reply	other threads:[~2007-08-04 17:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04 15:07 rc4 - make quick-install-doc is broken Mark Levedahl
2007-08-04 15:38 ` Johannes Schindelin
2007-08-04 16:00   ` Mark Levedahl
2007-08-04 16:04     ` Johannes Schindelin
2007-08-04 16:14       ` Mark Levedahl
2007-08-04 16:21         ` Johannes Schindelin
2007-08-04 17:56           ` Mark Levedahl [this message]
2007-08-04 21:32             ` [PATCH] Fix quick-install-doc Johannes Schindelin
2007-08-04 22:09               ` René Scharfe
2007-08-05  7:07                 ` [PATCH] Fix install-doc-quick target Junio C Hamano
2007-08-05 13:12                   ` Johannes Schindelin
2007-08-05 17:54                     ` Junio C Hamano
2007-08-05 18:10                       ` Johannes Schindelin
2007-08-05 14:44                   ` Johannes Schindelin
2007-08-06 22:43                   ` [PATCH] (Really) " Mark Levedahl
2007-08-06 22:50                     ` Johannes Schindelin
2007-08-06 23:07                       ` Junio C Hamano
2007-08-06 23:38                         ` Mark Levedahl
2007-08-06 23:43                           ` Johannes Schindelin
2007-08-06 23:49                             ` Mark Levedahl
2007-08-07  1:28                           ` Junio C Hamano
2007-08-07  1:55                             ` Mark Levedahl
2007-08-07  3:53                               ` Junio C Hamano
2007-08-07 13:55                                 ` René Scharfe
2007-08-07 14:08                                   ` Johannes Schindelin
2007-08-04 16:08     ` rc4 - make quick-install-doc is broken Mark Levedahl
2007-08-04 16:16       ` Johannes Schindelin
2007-08-04 16:27         ` Mark Levedahl
2007-08-04 20:19     ` René Scharfe
2007-08-04 20:21       ` Johannes Schindelin
2007-08-04 20:45       ` Mark Levedahl
2007-08-04 21:33       ` Johannes Schindelin
2007-08-04 22:09         ` René Scharfe
2007-08-04 22:25           ` Johannes Schindelin
2007-08-04 22:37           ` Johannes Schindelin
2007-08-04 23:03             ` René Scharfe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B4BDCF.9060809@gmail.com \
    --to=mlevedahl@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).