Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-cvs@linux-mips.org, linux-cvs-patches@linux-mips.org,
	linux-mips@linux-mips.org
Subject: CVS commit notification list and the git conversion
Date: Mon, 6 Mar 2006 17:57:32 +0000	[thread overview]
Message-ID: <20060306175732.GA18027@linux-mips.org> (raw)

As you may have noticed, the good old linux-cvs and linux-cvs-patches
mailing lists haven't received any postings since I converted the MIPS
kernel repository to git.  I now have the necessary bits and pieces in
places to resume the same kind of notifications with git.  I'm therefore
going to rename the two lists to linux-git rsp. linux-git-patches and will
have the notification catch up on postings that were not sent out due
since the conversion.

If you were subscribed to linux-cvs or linux-cvs-patches you will be
subscribed to the new list; there is nothing you will have to do.

As candy for procmail users the list has headers that looks like:
X-Git-Branch: master, X-Git-Branch: linux-2.4 etc. which can be used to
sort email.

As an implmentation choice I decieded to aggregate all commits merge from
kernel.org into a single mail rather than a large number of individual
mails, so it's going to be easier to follow what's really going on on
linux-mips.org.  In case you care about all the details of the changesets
from kernel.org as well I suggest you subscribe via majordomo to either
git-commits-head@vger.kernel.org to follow 2.6 development or
git-commits-24@vger.kernel.org for the 2.4 development.

  Ralf

                 reply	other threads:[~2006-03-06 17:49 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=20060306175732.GA18027@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-cvs-patches@linux-mips.org \
    --cc=linux-cvs@linux-mips.org \
    --cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox