From: Chris Wright <chrisw@sous-sol.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: xen-devel@lists.xensource.com, jeremy@xensource.com,
linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, joe@perches.com,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE
Date: Mon, 13 Aug 2007 12:19:38 -0700 [thread overview]
Message-ID: <20070813191938.GI3672@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070813121005.af159d1d.randy.dunlap@oracle.com>
* Randy Dunlap (randy.dunlap@oracle.com) wrote:
> On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > * joe@perches.com (joe@perches.com) wrote:
> > > +F: arch/i386/xen/
> > > +F: drivers/*/xen-*front.c
> > > +F: drivers/xen/
> > > +F: include/asm-i386/xen/
> > > +F: include/xen/
> >
> > I think this data will easily become stale. What is the point again?
>
> Agreed. But not everyone wants to or should have to use git,
> so what are the alternatives?
Between git (or gitweb), existing MAINTAINERS and a bit of common
sense (or extra sleuthing), I never perceived a significant problem.
Alternative could be to place info directly in source files. If not
all of MAINTAINERS info, it could be a tag to reference the relevant
MAINTAINERS entry.
thanks,
-chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wright <chrisw@sous-sol.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
joe@perches.com, xen-devel@lists.xensource.com,
virtualization@lists.osdl.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, jeremy@xensource.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE
Date: Mon, 13 Aug 2007 12:19:38 -0700 [thread overview]
Message-ID: <20070813191938.GI3672@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070813121005.af159d1d.randy.dunlap@oracle.com>
* Randy Dunlap (randy.dunlap@oracle.com) wrote:
> On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > * joe@perches.com (joe@perches.com) wrote:
> > > +F: arch/i386/xen/
> > > +F: drivers/*/xen-*front.c
> > > +F: drivers/xen/
> > > +F: include/asm-i386/xen/
> > > +F: include/xen/
> >
> > I think this data will easily become stale. What is the point again?
>
> Agreed. But not everyone wants to or should have to use git,
> so what are the alternatives?
Between git (or gitweb), existing MAINTAINERS and a bit of common
sense (or extra sleuthing), I never perceived a significant problem.
Alternative could be to place info directly in source files. If not
all of MAINTAINERS info, it could be a tag to reference the relevant
MAINTAINERS entry.
thanks,
-chris
next prev parent reply other threads:[~2007-08-13 19:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:39 [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE joe
2007-08-13 6:39 ` joe
2007-08-13 18:55 ` Chris Wright
2007-08-13 18:55 ` Chris Wright
2007-08-13 19:10 ` Randy Dunlap
2007-08-13 19:19 ` Chris Wright [this message]
2007-08-13 19:19 ` Chris Wright
2007-08-13 20:21 ` Adrian Bunk
2007-08-13 19:22 ` Valdis.Kletnieks
2007-08-13 19:22 ` Valdis.Kletnieks
2007-08-13 20:13 ` Adrian Bunk
2007-08-13 20:32 ` Valdis.Kletnieks
2007-08-13 20:47 ` Adrian Bunk
2007-08-13 20:54 ` Alan Cox
2007-08-13 20:54 ` Alan Cox
2007-08-13 21:33 ` Adrian Bunk
2007-08-13 19:13 ` Joe Perches
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=20070813191938.GI3672@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@linux-foundation.org \
--cc=jeremy@xensource.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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 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.