From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
Lars Kurth <lars.kurth@citrix.com>, Wei Liu <wei.liu2@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Committers <committers@xenproject.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/3] Docs: consolidate release related documents
Date: Mon, 31 Jul 2017 16:23:33 +0100 [thread overview]
Message-ID: <20170731152333.dtk4w2u72quiqwjd@citrix.com> (raw)
In-Reply-To: <22911.13785.793938.444012@mariner.uk.xensource.com>
On Mon, Jul 31, 2017 at 02:51:21PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 0/3] Docs: consolidate release related documents"):
> > Wei Liu (3):
> > docs: consolidate release related documents
> > docs: add xen-release-management.pandoc
> > docs: hook up process/ to build system
>
> FWIW,
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> However, AFAICT the mean reason this doesn't process
> release-checklist.txt and branching-checklist.txt into files on the
> website is that you only have it process pandocs.
>
Correct, that's deliberate.
> But I don't think those files are ever going to want to be made into
> web pages. Whereas it is possible that we will grow other process
> documents in .txt form which do, and no provision is made for them.
>
> I wonder if it would be better to rename those to files to a different
> directory. The reason I invented misc/ was precisely to avoid people
> (users and developers) tripping over them thinking they might be
> useful...
>
Lars (?) said there should be a "process" directory, hence I put
everything that's relevant here.
I'm open to suggestions about directory structure. Maybe having a
technician-checklist directory under process?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-31 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 11:22 [PATCH 0/3] Docs: consolidate release related documents Wei Liu
2017-07-31 11:22 ` [PATCH 1/3] docs: " Wei Liu
2017-07-31 11:22 ` [PATCH 2/3] docs: add xen-release-management.pandoc Wei Liu
2017-08-02 11:22 ` Juergen Gross
2017-08-08 11:03 ` Julien Grall
2017-08-08 16:41 ` Lars Kurth
2017-07-31 11:22 ` [PATCH 3/3] docs: hook up process/ to build system Wei Liu
2017-07-31 13:51 ` [PATCH 0/3] Docs: consolidate release related documents Ian Jackson
2017-07-31 15:23 ` Wei Liu [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=20170731152333.dtk4w2u72quiqwjd@citrix.com \
--to=wei.liu2@citrix.com \
--cc=committers@xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=xen-devel@lists.xenproject.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.