Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: wje@fir.esd.sgi.com (William J. Earl)
Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: CVS commit mailing list?
Date: Tue, 4 Jun 1996 10:16:42 -0700 (PDT)	[thread overview]
Message-ID: <199606041716.KAA28670@yon.engr.sgi.com> (raw)
In-Reply-To: <199606041618.JAA15088@fir.esd.sgi.com> from "William J. Earl" at Jun 4, 96 09:18:04 am

OK, I requested

	linux-progress

to be created on majordomo@engr.

I guess it'll take some time till someone gets time to set this up,
I'll let you know when it is ready.


>
>Ariel Faigon writes:
> > 
> > If anyone on the linux@engr list is _not_ interested in these
> > CVS commit auto reports, let me know and I'll ask majordomo-owner
> > to create a separate:
> > 
> > 	linux-progress@engr
> > 
> > majordomo list.
> > 
> > Until we see objections/too-much-traffic, I think Dave can
> > go ahead and auto-mail the reports to linux@engr
> > 
> > Personally, I think I'll find these interesting.
>...
>
>      I am interested too, but I would rather have two lists, just as
>we normally do for regular development (sgi.bugs.xxx for bug reports and
>checkins about xxx, sgi.engr.xxx for general discussion about xxx).  
>Why don't you set up linux-progress as a clone of linux to start, and 
>people who tire of the reports can unsubscribe from the linux-progress.
>Having a separate list will also make a little easier to search the
>archives later on.
>


-- 
Peace, Ariel

WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: "William J. Earl" <wje@fir.esd.sgi.com>
Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: CVS commit mailing list?
Date: Tue, 4 Jun 1996 10:16:42 -0700 (PDT)	[thread overview]
Message-ID: <199606041716.KAA28670@yon.engr.sgi.com> (raw)
Message-ID: <19960604171642.Q8VpZSOICZTyqrAs70qjUUUa_bge_W5FOGuBpzcPBBc@z> (raw)
In-Reply-To: <199606041618.JAA15088@fir.esd.sgi.com> from "William J. Earl" at Jun 4, 96 09:18:04 am

OK, I requested

	linux-progress

to be created on majordomo@engr.

I guess it'll take some time till someone gets time to set this up,
I'll let you know when it is ready.


>
>Ariel Faigon writes:
> > 
> > If anyone on the linux@engr list is _not_ interested in these
> > CVS commit auto reports, let me know and I'll ask majordomo-owner
> > to create a separate:
> > 
> > 	linux-progress@engr
> > 
> > majordomo list.
> > 
> > Until we see objections/too-much-traffic, I think Dave can
> > go ahead and auto-mail the reports to linux@engr
> > 
> > Personally, I think I'll find these interesting.
>...
>
>      I am interested too, but I would rather have two lists, just as
>we normally do for regular development (sgi.bugs.xxx for bug reports and
>checkins about xxx, sgi.engr.xxx for general discussion about xxx).  
>Why don't you set up linux-progress as a clone of linux to start, and 
>people who tire of the reports can unsubscribe from the linux-progress.
>Having a separate list will also make a little easier to search the
>archives later on.
>


-- 
Peace, Ariel

  reply	other threads:[~1996-06-04 18:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-04  7:46 CVS commit mailing list? Ariel Faigon
1996-06-04 12:15 ` Kwesi Ames
1996-06-04 16:18 ` William J. Earl
1996-06-04 17:16   ` Ariel Faigon [this message]
1996-06-04 17:16     ` Ariel Faigon
1996-06-05  6:42     ` David S. Miller
1996-06-05  6:42       ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
1996-06-04  5:03 David S. Miller

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=199606041716.KAA28670@yon.engr.sgi.com \
    --to=ariel@yon.engr.sgi.com \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=wje@fir.esd.sgi.com \
    /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