From: Junio C Hamano <junkio@cox.net>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org, "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Subject: Re: Generating docu in 1.4.3.3.g01929
Date: Sat, 28 Oct 2006 12:22:59 -0700 [thread overview]
Message-ID: <7v7iyk8cto.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <BAYC1-PASMTP11A0267A1CE74A17EDE925AE050@CEZ.ICE> (seanlkml@sympatico.ca's message of "Sat, 28 Oct 2006 15:13:54 -0400")
Sean <seanlkml@sympatico.ca> writes:
>> So the difference between me and Horst that can be bisected is
>> not what are listed above. I wonder what other things come into
>> the picture.
>
> The thing is, Horst implied everything worked before a recent pull.
Ah, Ok.
I explicitly asked about things that would help to narrow down
and Horst did not answer to any, so I took that "no info" as (0)
this is the first doc generation so it is unknown if older git
sources would generate docs correctly in the environment, (1)
not just git-daemon.1 but generating git-anything.1 is broken,
(2) not just git-daemon.1 but generating git-daemon.html is also
broken.
You interpreted the "no info" differently, which is valid.
> It's worth at least going back to see if that's true. Quite likely
> that older version will no longer work anymore either, but maybe it
> will. Of course, if an older version no longer works, there's no
> need to bisect further, something in the environment has changed.
> Either way, it'll help narrow things down a bit.
Very true.
next prev parent reply other threads:[~2006-10-28 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 17:26 Generating docu in 1.4.3.3.g01929 Horst H. von Brand
2006-10-27 19:44 ` Sean
[not found] ` <20061027154433.da9b29d7.seanlkml@sympatico.ca>
2006-10-27 23:12 ` Horst H. von Brand
2006-10-28 4:24 ` Sean
2006-10-28 5:45 ` Junio C Hamano
2006-10-28 6:07 ` Sean
2006-10-28 19:04 ` Junio C Hamano
2006-10-28 19:13 ` Sean
2006-10-28 19:22 ` Junio C Hamano [this message]
2006-10-29 19:03 ` Horst H. von Brand
2006-10-27 21:34 ` Junio C Hamano
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=7v7iyk8cto.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
--cc=vonbrand@inf.utfsm.cl \
/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