From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
Cc: unlisted-recipients:; (no To-header on input) Bert Wesarg
<bert.wesarg@googlemail.com>,
Josef 'Jeff' Sipek <jeffpc@josefsipek.net>,
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: Tue, 09 Sep 2008 08:13:20 -0700 [thread overview]
Message-ID: <7vd4jd8i9b.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <48C673CF.2000107@fastmail.fm> (Michael J. Gruber's message of "Tue, 09 Sep 2008 15:02:07 +0200")
Michael J Gruber <michaeljgruber+gmane@fastmail.fm> writes:
> I would go about renaming quick-install-doc to quick-install-man, introducing quick-install-html doing the analogous using the "html" branch and quick-install-doc doing both, which would be more in line with the install-doc target.
>
> Are there any objections to renaming quick-install-doc to quick-install-man?
What does it improve?
IOW, can't you do what you want to do (I am assuming that what you want to
do is to be able to copy out the pregenerated contents from convenience
branches) without such a rename?
If you rename the target, I am reasonably sure you would break somebody's
build procedure. It is a separate topic if there are large number of such
somebody, or just a limited few.
next prev parent reply other threads:[~2008-09-09 15:14 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
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 [this message]
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=7vd4jd8i9b.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=michaeljgruber+gmane@fastmail.fm \
/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).