All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Wiki write access disabled?
Date: Thu, 13 Oct 2011 13:06:44 -0400	[thread overview]
Message-ID: <20111013170644.GI26170@denix.org> (raw)
In-Reply-To: <4E957C19.6080106@slimlogic.co.uk>

On Wed, Oct 12, 2011 at 12:38:01PM +0100, Graeme Gregory wrote:
> Did some experiments with FM on IRC, seems you need the approved flag to be 
> sat to edit wiki now.
>
> I don't know what the procedure is to set this flag. I have set it for 
> eFfeM now. I don't want to go ahead and add it for other users without a 
> nod from someone who knows more about the wiki than me.

So, how do we go about this limitation? Do we enable write access on a case by 
case basis? Right now I believe there is only a handful of people allowed to 
edit Wiki pages...

-- 
Denys


> I also note the virtual hosting of wiki.openembedded.org/.net is not quite 
> working.  You can't log in to .org and all pages seem to be missing on .net 
> domain.
>
> Graeme
>
>
> On 12/10/11 08:31, Ulf Samuelsson wrote:
>> Noticed that the wiki seems to be wrong on the 2011.03 release.
>>
>> http://www.openembedded.org/wiki/Release-2011.03
>>
>> The page tells you to:
>>
>> git checkout release-2011.03
>>
>> or
>>
>> git checkout -b release-2011.03 origin/release-2011.03
>>
>> I tried, and that failed.
>>
>> $ git checkout -b ulf/release-2011.03-2011-10-12 origin/release-2011.03
>>
>> and got the error message.
>>
>> fatal: git checkout: updating paths is incompatible with switching 
>> branches.
>> Did you intend to checkout 'origin/release-2011.03' which can not be 
>> resolved as commit?
>>
>> $ git remote show origin
>> did not show any "release-2011.03", but there is a "2011.03-maintenance"
>> which I guess is what you want.
>>
>> Tried to change the "http://www.openembedded.org/wiki/Release-2011.03" 
>> wiki page
>> to reflect this, but that was not possible, since I did not have write 
>> access any longer.
>>
>> Has the rules changed, or is this a mistake in configuration.
>>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  parent reply	other threads:[~2011-10-13 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12  7:31 Wiki write access disabled? Ulf Samuelsson
2011-10-12 11:38 ` Graeme Gregory
2011-10-12 15:09   ` Philip Balister
2011-10-13 17:06   ` Denys Dmytriyenko [this message]
2011-10-13 17:51     ` Graeme Gregory

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=20111013170644.GI26170@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.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.