git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	guilt@lists.josefsipek.net, "Brandon Philips" <brandon@ifup.org>
Subject: Re: [ANNOUNCE] Guilt v0.31
Date: Mon, 8 Sep 2008 20:50:03 +0200	[thread overview]
Message-ID: <36ca99e90809081150v4ad6e7a0n72b5cca39e02b1bc@mail.gmail.com> (raw)
In-Reply-To: <20080908184322.GE27550@josefsipek.net>

On Mon, Sep 8, 2008 at 20:43, Josef 'Jeff' Sipek <jeffpc@josefsipek.net> wrote:
> On Mon, Sep 08, 2008 at 08:33:23PM +0200, Bert Wesarg wrote:
>> Hi,
>>
>> On Mon, Sep 8, 2008 at 15:52, Josef 'Jeff' Sipek <jeffpc@josefsipek.net> wrote:
>> > Guilt v0.31 is available for download.
>>
>> Is it possible to include pre-generated docs in the tarballs?
>>
>> I downloaded one and run 'make doc' and get these messages:
>>
>> fatal: Not a git repository
>>
>> which looks like it comes from this line in Documentation/Makefile:
>>
>> VERSION=$(shell git describe)
>>
>> Its not critical, but looks awkward.
>
> 1) I already commit generated man pages for each release - on the man branch
>   (there's also html branch with the html-formated man pages).
>
> 2) I'm aware of the git error you saw, and it is on my todo list
>
> 3) I just checked the git tarballs, and they don't include man pages either.
>   Should I include the manpages in the source tarball, or should I just
>   create another tarball with the manpages? (The git error will get fixed
>   regardless - that's the only invocation of git during the manpage build
>   process, and it's there only to get a nice looking version number to
>   include in the manpages.)
I must admit, that I don't like these extra tarballs with docs. I
always expect, that the manpages are nicely installed if I type 'make
install' (or at least with a install-doc target). But I need to
download this extra package, and extract it to the right place, there
is no Makefile whatsoever. In case of git its really annoying, because
the help mechanism is relying on the manpages (i.e. git help <cmd> or
git <cmd> --help, but you know this).

Thanks
Bert
>
> Josef 'Jeff' Sipek.

  reply	other threads:[~2008-09-08 18:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 13:52 [ANNOUNCE] Guilt v0.31 Josef 'Jeff' Sipek
2008-09-08 15:39 ` Michael J Gruber
2008-09-08 15:45   ` Josef 'Jeff' Sipek
2008-09-08 15:58   ` Josef 'Jeff' Sipek
2008-09-08 18:33 ` Bert Wesarg
2008-09-08 18:43   ` Josef 'Jeff' Sipek
2008-09-08 18:50     ` Bert Wesarg [this message]
2008-09-08 19:17       ` Junio C Hamano
2008-09-09 10:10         ` Michael J Gruber
2008-09-09 13:02           ` Michael J Gruber
2008-09-09 15:13             ` Junio C Hamano
2008-09-09 15:40               ` Michael J Gruber
2008-09-09 16:02                 ` Junio C Hamano
2008-09-09 16:29                   ` Michael J Gruber

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=36ca99e90809081150v4ad6e7a0n72b5cca39e02b1bc@mail.gmail.com \
    --to=bert.wesarg@googlemail.com \
    --cc=brandon@ifup.org \
    --cc=git@vger.kernel.org \
    --cc=guilt@lists.josefsipek.net \
    --cc=jeffpc@josefsipek.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).