From: Junio C Hamano <junkio@cox.net>
To: Coywolf Qi Hunt <qiyong@fc-cn.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUCNE] GIT 1.1.0
Date: Mon, 09 Jan 2006 02:38:30 -0800 [thread overview]
Message-ID: <7vbqylpty1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vr77hpwla.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Mon, 09 Jan 2006 01:41:21 -0800")
Junio C Hamano <junkio@cox.net> writes:
> Coywolf Qi Hunt <qiyong@fc-cn.com> writes:
>
>> Why not support debian? I see the debian directory is outdated.
>
> I think that was discussed already this year, so look in the
> list archive for the past 10 days or so please before asking.
Especially, please see this thread:
http://marc.theaimsgroup.com/?l=git&m=113576889301331
I haven't received any patches to re-add debian/ directory from
Gerrit since I removed it, and I do not expect nor wish to get
one. I respect Gerrit's request not to ship debian/ directory
myself.
If you want to see deb packages at kernel.org built by me, you
need to convince both Gerrit and me with a workable workflow
that does not add extra burden on us and avoids confusion.
A starting point might be for me to slave debian/ part from
Gerrit, updating debian/changelog with only X.Y.Z-0 entries by
me, and publish X.Y.Z-0 packages at kernel.org.
next prev parent reply other threads:[~2006-01-09 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 1:20 [ANNOUCNE] GIT 1.1.0 Junio C Hamano
2006-01-09 8:49 ` Coywolf Qi Hunt
2006-01-09 9:41 ` Junio C Hamano
2006-01-09 10:38 ` Junio C Hamano [this message]
2006-01-09 11:09 ` Martin Langhoff
2006-01-11 9:25 ` Gerrit Pape
2006-01-09 20:43 ` lamikr
2006-01-09 22:22 ` Andreas Ericsson
2006-01-09 22:59 ` Junio C Hamano
2006-01-09 23:55 ` lamikr
2006-01-10 0:22 ` Andreas Ericsson
2006-01-10 1:21 ` Junio C Hamano
2006-01-10 14:49 ` Johannes Schindelin
2006-01-10 0:28 ` Junio C Hamano
2006-01-10 2:00 ` H. Peter Anvin
2006-01-10 3:05 ` 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=7vbqylpty1.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=qiyong@fc-cn.com \
/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).