On Friday 30 May 2008 08:42:27 am Stefano Zacchiroli wrote:
On Fri, May 30, 2008 at 12:33:01AM +0200, sean finney wrote:
one open question i have now is with regards to the eventual hosting of
the system: does it seem reasonable that the final version could either
coexist on an existing
On Friday 30 May 2008 08:32:18 am Lucas Nussbaum wrote:
How much static content will you have? I mean: it's not like this
service will receive millions of requests per day. It could be better to
have only a few static pages, and do everything else on-demand.
well, i'm taking a fairly
On Fri, May 30, 2008 at 12:33:01AM +0200, sean finney wrote:
one open question i have now is with regards to the eventual hosting of the
system: does it seem reasonable that the final version could either coexist
on an existing archive, or alternatively have enough space for the .dsc
and
On 30/05/08 at 00:33 +0200, sean finney wrote:
hi folks,
just a quick update, the PoC that i was doing was quickly getting
complicated
enough that i've abandoned it in favor of an initial implementation code that
will hopefully be useful in the final version as well. thus it has
Lucas Nussbaum wrote:
patches.debian.org
==
Objective:
Provide simple place to learn about Debian-specific patches, for
upstream, users and other DDs.
Features: browsing patches, downloading them, tracking status of
patches.
Split .diff.gz to extract patches for:
hi folks,
just a quick update, the PoC that i was doing was quickly getting complicated
enough that i've abandoned it in favor of an initial implementation code that
will hopefully be useful in the final version as well. thus it has
introduced some more delay, as i was evaluating a few
On 20/05/08 at 21:01 +0200, sean finney wrote:
hi,
this is both a request and an notice of intent that i may try to
implement something :)
Hi Sean,
Have you had time to work on something?
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]
hiya,
Hi Sean,
Have you had time to work on something?
progress was slower than i would have liked, but yes there's progress. i
should have something to show in a day or two.
sean
signature.asc
Description: This is a digitally signed message part.
On 20/05/08 at 21:01 +0200, sean finney wrote:
Package: qa.debian.org
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
this is both a request and an notice of intent that i may try to
implement something :)
my proposal is that the current patches section on a
On Tue, 20 May 2008, sean finney wrote:
my proposal is that the current patches section on a source package's
qa package is modified so that the following information is somehow
provided, where appropriate (depending on structure/format of source
package naturally).
- - entire debian patch
hiya,
On Wednesday 21 May 2008 07:02:30 am Lucas Nussbaum wrote:
What you propose sounds like adding a lot of information to the PTS
page. Why did you choose that, instead of a separate website
(http://patches.d.o)?
after looking over the sources for the pts, i agree that the best place to do
oh, missed some comments at the top:
On Wednesday 21 May 2008 08:56:20 am Raphael Hertzog wrote:
It really looks like the patches.debian.org discussed on -devel. ;-)
if it's in that debian patches discussion, i killfiled the whole thing
because the S:N ratio was getting a little low. but i
hiya,
On Wednesday 21 May 2008 08:56:20 am Raphael Hertzog wrote:
It could possibly be mole-based so that it can automatically process any
new source package that gets uploaded to Debian.
http://qa.debian.org/cgi-bin/mole/doc
(The table devpackages-src would be your TodoSource)
thanks for
On Wed, 21 May 2008, sean finney wrote:
Various other considerations that I'd like to add:
- make it cross-distro from the beginning so that it can contain patches
from multiple distributions (ie each patch is associated with one or
more distros)
interesting. i don't see any reason
On 21/05/08 at 09:03 +0200, sean finney wrote:
additionally, for each patch, when possible provide the following
information:
- - which version of the package introduced it
how are you planning to determine that? why is that important?
how is perhaps left for future exploration,
On 21/05/08 at 08:56 +0200, Raphael Hertzog wrote:
Various other considerations that I'd like to add:
- make it cross-distro from the beginning so that it can contain patches
from multiple distributions (ie each patch is associated with one or
more distros)
I really don't think that it is
Here is what I wrote down about this patches.d.o idea (sorry, it's not
very well organized, and doesn't include some ideas mentioned in the
-devel@ thread).
patches.debian.org
==
Objective:
Provide simple place to learn about Debian-specific patches, for
upstream, users and
Package: qa.debian.org
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
this is both a request and an notice of intent that i may try to
implement something :)
my proposal is that the current patches section on a source package's
qa package is modified so that the following
18 matches
Mail list logo
