From: Junio C Hamano <junkio@cox.net>
To: Gerrit Pape <pape@smarden.org>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4
Date: Mon, 05 Dec 2005 12:16:37 -0800 [thread overview]
Message-ID: <7vu0dnb8pm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051205172601.4980.qmail@67565db8368c55.315fe32.mid.smarden.org> (Gerrit Pape's message of "Mon, 5 Dec 2005 18:26:01 +0100")
Gerrit Pape <pape@smarden.org> writes:
> On Sun, Dec 04, 2005 at 01:21:13AM -0800, Junio C Hamano wrote:
>> *1* It appears Debian finally has an official maintainer, so I
>
> Yes, I've taken over maintainership, and introduced the git-core package
> into Debian/unstable, the git tools previously were included in the
> cogito package.
This question is probably relevant only to you and people who
want to build deb themselves until you package the updated
upstream, but what is your (and others') preference on debian/
directory in what _I_ ship?
I see three possibilities:
- Do not care, and keep them as they are as they bitrot.
- Remove debian/ from the upstream tree.
- You feed patches to me, and I promise you not to touch
debian/ area, except adding a new -0 entry at the top of the
changelog when bumping the version number up, and perhaps
adjusting to the main Makefile changes if the solution is
obvious.
I am neutral between the second and the third.
next prev parent reply other threads:[~2005-12-05 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 9:21 [ANNOUNCE] GIT 0.99.9l aka 1.0rc4 Junio C Hamano
2005-12-04 20:16 ` Horst von Brand
2005-12-04 20:49 ` H. Peter Anvin
2005-12-05 17:26 ` Gerrit Pape
2005-12-05 20:16 ` Junio C Hamano [this message]
2005-12-05 21:10 ` Jon Loeliger
2005-12-07 16:20 ` Gerrit Pape
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=7vu0dnb8pm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pape@smarden.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).