From: Mark Wielaard <mark@klomp.org>
To: Thomas Girard <thomas.g.girard@free.fr>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: Questions about build web documentation
Date: Tue, 21 Aug 2007 07:31:00 -0000 [thread overview]
Message-ID: <1187681465.3852.6.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1187647127.3856.25.camel@micmac>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Hi Thomas,
On Mon, 2007-08-20 at 23:58 +0200, Thomas Girard wrote:
> Le lundi 20 août 2007 à 16:28 -0500, Phil Muldoon a écrit :
> > > I'm wondering if tracker bugs sould be split for Ubuntu and Debian
> > > releases the way they are for Red Hat?
> >
> > Is there a casual or implied relationship between Ubuntu and Debian that
> > is on-going? Other than Ubuntu was derived from Debian. If not, then
> > they should be treated as different products, with different trackers?
>
> Sorry, my question was misleading: Ubuntu and Debian already have
> different trackers. But there is a single tracker for all Ubuntu
> releases, and another single one for all Debian releases. Red Hat on the
> other hand has a tracker bug for RHEL4, another one for RHEL5.
Yes, and similar for Fedora releases. Since frysk is somewhat dependent
on the specific compiler and kernel used it makes sense to have
different trackers for distro releases where those components are
different.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-08-21 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 8:27 Thomas Girard
2007-08-09 10:24 ` Mark Wielaard
2007-08-12 20:38 ` Thomas Girard
2007-08-20 21:28 ` Phil Muldoon
2007-08-20 22:02 ` Thomas Girard
2007-08-21 7:31 ` Mark Wielaard [this message]
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=1187681465.3852.6.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=thomas.g.girard@free.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).