All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Lord <lord@emf.net>
To: linux-kernel@vger.kernel.org
Cc: arch-users@lists.fifthvision.net, dev@subversion.tigris.org,
	opencm-dev@smtp.opencm.org, jmacd@users.sourceforge.net
Subject: moving the BitBucket GPL discussion to a context with potential for _progress_
Date: Sat, 15 Mar 2003 20:06:08 -0800 (PST)	[thread overview]
Message-ID: <200303160406.UAA11523@emf.net> (raw)



[PLEASE ... DO NOT followup without trimming the addressees.]

	David Lang (on lkml, in the context of a partly interesing
	revision control system discussion):

        hey guys, the suggestion to move to another list for this
        discussion was to reduce traffic on the kernel list, not add a
        bunch of arch discussions to the bitkeeper discussions.


First, please tolerate _some_ (hopefully very _short_ term)
cross-posting as a tactic to move the discussion to the
arch-users@lists.fifthvision.net list.  Honestly, I think a few
redundant declarations on lkml can help with the medium-to-longer-term
movement of traffic off of lkml.  (Not that your plea is inconsistent
with that.)

Second, I personally (taking a risk here) think it's reasonable to use
arch-users for more than just the narrow arch topic -- for the whole
lkml-vs.-bk issue, for example.  arch-users are already learning from
these lkml threads.  If you're *really* off-topic on arch-users, but
have made what you think is an enriching post, just put "OT:" in the
subject line (but, hey, make it a _high quality_ post, whatever that
means).

Third, in the arch world, I think we're really open-minded and
interested about revision control in general -- we're thinking a lot
about design issues -- not slavishly devoted to just a narrow
conception of arch.  Projects that compete with arch -- developers of
competing systems -- let's (M. Grubb, forgive me for not getting prior
permission :-), gather on arch-users for rational discourse.

I'll leave you with the enclosed, from arch-users.  We _are_ conscious
of de-noisifying lkml (and not needlessly noisifying any other list or
mbox).

-t

Subject: [arch-users] the "zen" of lkml

Here, let me try to say nothing at all:

*) On the one hand, if several of us say essentially the same
   thing on lkml, but in different terms, that greatly increases
   the chances of achieving communication.


*) On the other hand, if several of us say essentially the same
   thing on lkml, but in different terms, that greatly increases
   the chances of dragging out an unwelcome thread.


I don't know what that means but it sounds important so keep it in
mind.


-t

_______________________________________________
arch-users mailing list
arch-users@lists.fifthvision.net
http://lists.fifthvision.net/mailman/listinfo/arch-users




                 reply	other threads:[~2003-03-16  3:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200303160406.UAA11523@emf.net \
    --to=lord@emf.net \
    --cc=arch-users@lists.fifthvision.net \
    --cc=dev@subversion.tigris.org \
    --cc=jmacd@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opencm-dev@smtp.opencm.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.