Maintainers Guide
The Debian Hamradio Maintainers Guide is a document that outlines team
policy and best current practice for the Deian Hamradio Maintainers
packaging team.
The documentation is installed in both HTML and PDF format.
escreveu:
Pessoal, quero traduzir o Debian New Maintainers' Guide para pt-br.
Alguém conheçe alguém que já começou, pra não fazer duas vezes o
mesmo serviço.
Caso afirmativo, favor responder este email.
http://www.debian.org/doc/maint-guide/index.pt-br.html
- --
Saudações,
Italo
Hi,
On Sat, Jan 26, 2008 at 12:40:14AM +0900, Osamu Aoki wrote:
This seems to be much cleaner than dpatch or quilt. Also with the help
of gitk, history is much more visible. I look forward to see it matured
and accepted.
personally I am a fan of the diversity in the Debian project. Its
On Tue, Feb 05, 2008 at 06:24:38PM +, Patrick Schoenfeld wrote:
So, I would agree with those recommending quilt, if it has significant
pros besides dpatch. That would be forcing to a specific tool and so
giving up some diversity, but it would keep giving up freedom of choice
on a low
Hmmm...
On Fri, Jan 25, 2008 at 10:51:41PM +0900, Osamu Aoki wrote:
I ended up updating NM guide which only had dpatch to current one with
quilt:
http://www.debian.org/doc/manuals/maint-guide/ch-build.en.html#s-dpatch
As I read this thread back to d-project, ... interesting. It all started
Hi,
On Fri, Jan 25, 2008 at 10:51:05AM +0100, Lucas Nussbaum wrote:
On 25/01/08 at 08:01 +, Steve Langasek wrote:
As a second runner up, quilt is ok by me. :)
I made some stats (see [1]). 7.8% of our packages use quilt, while 14.4%
use dpatch.
This was discussed in debian-doc and
[Please keep CC]
Where should the bugs found in Debian New Maintainers' Guide be
reported? BTS package name?
Jari
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
HellO!
On Sun, 07 Jan 2007 18:02:34 +0100, Jari Aalto wrote:
Where should the bugs found in Debian New Maintainers' Guide be
reported? BTS package name?
=
[EMAIL PROTECTED]:~$ dpkg -s maint-guide | grep Description
Description: Debian New Maintainers' Guide
[EMAIL PROTECTED]:~$
=
Thx
On Sun, Jan 07, 2007, Jari Aalto wrote:
Where should the bugs found in Debian New Maintainers' Guide be
reported? BTS package name?
maint-guide
[no Cc:, I read the list]
--
Mohammed Adnène Trojette
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jari Aalto wrote:
[Please keep CC]
Where should the bugs found in Debian New Maintainers' Guide be
reported? BTS package name?
maint-guide?
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=maint-guide
Best Regards,
Andreas
* Anthony DeRobertis
| Well, isn't prohibiting the I didn't know it is copyrighted defence
| the only legal effect of having the notice nowadays, anyway?
Are you able to claim that source code written is not under copyright
in any way? It's less than 70 years after the author's death (even
for
Tollef Fog Heen writes:
Are you able to claim that source code written is not under copyright in
any way? It's less than 70 years after the author's death (even for
really old code from, say, 1950) and if it clearly is copyrightable, it
will be under copyright.
If it was written by a US
Hello Anthony,
Anthony DeRobertis [EMAIL PROTECTED] wrote:
Jeremy Stanley wrote:
This has to include a copyright year, also.
...and following additional discussion, the resolution is:
After considering the suggestion, I have decided to close this
bug.
The year really should
Scripsit Anthony DeRobertis [EMAIL PROTECTED]
On Tue, Mar 28, 2006 at 03:51:30PM +0200, Henning Makholm wrote:
Only for some pretty strange values of worthless. AFAIU the only
legal effect of the notice requirements you cite is as defined by
subsection (d): if a compliant notice is present, a
Scripsit Anthony DeRobertis [EMAIL PROTECTED]
The year really should be included. At least in the US, not having a
year in the notice appears to make the notice worthless. Quoting Title
17 USC Sec. 401(b):
Only for some pretty strange values of worthless. AFAIU the only
legal effect of the
On Tue, Mar 28, 2006 at 03:51:30PM +0200, Henning Makholm wrote:
Only for some pretty strange values of worthless. AFAIU the only
legal effect of the notice requirements you cite is as defined by
subsection (d): if a compliant notice is present, a defendant is
excluded from the defense that
]. Please read that *now*.
[1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.html
[...]
Why not add this to the New Maintainers Guide instead of
forcing Applicants to search the mailing list archive for
this?
Feel free to submit patches to wherever it may get added.
I
Jeremy Stanley wrote:
This has to include a copyright year, also.
...and following additional discussion, the resolution is:
After considering the suggestion, I have decided to close this
bug.
The year really should be included. At least in the US, not having a
year in the notice
Maintainers Guide instead of
forcing Applicants to search the mailing list archive for
this?
Regards Nico
--
Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF
http://www.ngolde.de | http://www.muttng.org | http://grml.org
Forget about that mouse with 3/4/5 buttons -
gimme a keyboard with 103/104/105
[...]
Why not add this to the New Maintainers Guide instead of
forcing Applicants to search the mailing list archive for
this?
Feel free to submit patches to wherever it may get added.
--
bye Joerg
Starting network management services:
Warning: -s option is deprecated, use -Lsd instead
Uah
/12/msg7.html
[...]
Why not add this to the New Maintainers Guide instead of
forcing Applicants to search the mailing list archive for
this?
Furthermore, the format given in the message is dissimilar from what
dh_make (0.40) gives right now. The default is...
This package
I just can't locate copyright statement anywhere within the package --
only license file (MPL 1.1/GPL 2.0/LGPL 2.1)
is copyright assumed to belong to upstream author? what years then
should be mentioned?
--
.-.
=-- /v\
-devel-announce/2003/12/msg7.html
[...]
Why not add this to the New Maintainers Guide instead of
forcing Applicants to search the mailing list archive for
this?
Feel free to submit patches to wherever it may get added.
I suggest to add it to the Developer's Reference instead
23 matches
Mail list logo
