From: Marian Csontos <mcsontos@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Frank Eigler <fche@redhat.com>, overseers@sourceware.org
Subject: Re: Questions about Sourceware
Date: Thu, 09 Mar 2017 17:31:00 -0000 [thread overview]
Message-ID: <61cb52d7-b780-dcb5-5950-5ddf1852fc3d@redhat.com> (raw)
In-Reply-To: <20170309155526.GC3979@elastic.org>
On 03/09/2017 04:55 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> [...]
>> For each ikiwiki there will be needed:
>> 2 public accessible group writable git repos - setup and content, somewhere
>> under $poject-home, linked from /git,...
>>
>> How to create them?
>> - Ask overseers to have them created for us.
>
> ^^ this.
>
>> These will be checked out from the above git repos. As generated
>> content, should this be under /sourceware/projects or is there
>> another preferred location?
>
> There will be a project home directory made for you.
Is it /sourceware/projects/lvm2-home ?
Or more likely /sourceware/something-else/lvm2, which would make e.g.
rsync bit easier ?
Whatever, I can now start with scripting, and will update as we agree on
the final locations. Will push to a git repo too, so if there is anyone
setting another wiki, or cloning and contributing, it could be reused.
Thanks!
-- Martian
>
>
>> And few more related questions:
>> Shall I send you script(s) for */sourceware/infra/bin/*?
>> ...and if so, as ikiwiki's auto.setup is interactive, is command
>> line preferred, or is interactive accepted as well?
>
> Do these need to go into infra/bin? If they are for ikiwiki only,
> you could put them under some /bin subtree of your own.
>
>> [...]
>> May I ask, why sourceware does not use gitweb's automatic repo search?
>
> Not sure; maybe that wasn't available in the prehistoric versions when
> we first set them up.
>
>> Would it mean less work for you, if groups had group writable
>> directory under /git, /sourceware/www/sourceware/htdocs/git/,...?
>> [...]
>
> It depends on how many such repos you will end up needing. If it's
> just the one or two, don't worry about it; our symlink widgetry will
> do. If it's a slew, then something like the cygwin-apps/ structure
> will be needed.
>
>
> - FChE
>
prev parent reply other threads:[~2017-03-09 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 15:14 Marian Csontos
2017-03-09 15:55 ` Frank Ch. Eigler
2017-03-09 17:31 ` Marian Csontos [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=61cb52d7-b780-dcb5-5950-5ddf1852fc3d@redhat.com \
--to=mcsontos@redhat.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).