Russ Allbery <[EMAIL PROTECTED]> writes:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>> sensible_editor ./debian/changelog # add in ./debian/changes/
>> <>
>> git tag -s v3.8.0.0
>> git push origin
>> --8<---cut here---end--->8---
>
> Yup, that looks right fo
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> We can adopt a policy of recording the proposer and seconder of
> an change in ./debian/changelog; as well as the commit message; since
> really, unlike code, wording proposal and review are integral to good
> policy development, and people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Russ Allbery wrote:
>
> For kill, XSI is what permits kill -1 or kill -HUP. POSIX without XSI
> requires kill -s HUP (no numbers allowed and -s required). This is a bit
> more than just the signal number thing, but I think it's reasonable to
> permi
On Wed, 30 Apr 2008 12:22:53 -0700, Russ Allbery <[EMAIL PROTECTED]> said:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>> I think the new commit goes on the branch, logically speaking, since
>> it is part of getting the branch ready. And we really have two
>> seconders sending in an ack, and w
On Wed, 30 Apr 2008 12:27:25 -0700, Russ Allbery <[EMAIL PROTECTED]> said:
> While preparing the next release, should I delete ChangeLog and
> debian/ChangeLog? It doesn't look like either have been used in a
> while, and since we're using a VCS that records all that information
> with more deta
While preparing the next release, should I delete ChangeLog and
debian/ChangeLog? It doesn't look like either have been used in a while,
and since we're using a VCS that records all that information with more
detail, I wouldn't think we'd want to use it in the future.
Also, debian/postinst.in, de
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> I think the new commit goes on the branch, logically speaking,
> since it is part of getting the branch ready. And we really have two
> seconders sending in an ack, and we can record them separately, unless
> they come in close together. In
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Well, I think we ought to go with recommend/may, and use the
> footnote to say that it will become should/recommend forthwith, and
> people should take note.
Okay, I can tackle a rewording along those lines.
> Doing the latter is
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> OK. We should get a sign off from dpkg folks to ensure they are
> on the same page as the policy folks about which bits of the API are
> features the project depends on and has a reasonable expectation of not
> changing.
Yup, I agree with
Hi,
On Sun, 2008-04-27 at 19:04:44 -0700, Russ Allbery wrote:
> Here is a proposed patch that also clarifies the comparison of version
> numbers a bit. Seconds?
>
> diff --git a/policy.sgml b/policy.sgml
> index 1c9a339..b7ac92e 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -2877,19 +2877,
Should policy require, or at least strongly recommend,
that:
1. Each package that create _one_ or more
configuration file in /etc should put them in a
dedicated directory, for example as /etc/sourceName/.
That directory might be a natural place for user
modifications, breaking a long conf file when
On Tue, 29 Apr 2008 23:35:33 -0700, Russ Allbery <[EMAIL PROTECTED]> said:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>> On Tue, 29 Apr 2008 22:10:41 -0700, Russ Allbery <[EMAIL PROTECTED]>
>> said:
>>> Manoj Srivastava <[EMAIL PROTECTED]> writes:
The following patch, from branch bug458
12 matches
Mail list logo
