All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	<xen-devel@lists.xenproject.org>,
	Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v1] automation: collect log files in subdirectories
Date: Fri, 16 Jul 2021 15:28:43 +0100	[thread overview]
Message-ID: <YPGXm9F3OHqLk/ml@perard> (raw)
In-Reply-To: <20210714093104.52f25e70.olaf@aepfle.de>

On Wed, Jul 14, 2021 at 09:31:04AM +0200, Olaf Hering wrote:
> Am Thu, 8 Jul 2021 12:43:41 +0100
> schrieb Andrew Cooper <andrew.cooper3@citrix.com>:
> 
> > As for testing, get an account on Gitlab.  I'll add you to xen-project,
> > after which pushes to your local fork of Xen here will use the
> > project-wide runner configuration, rather than using the Gitlab's pool
> > of public workers (which amongst other things, lack ARM).
> 
> Now there is https://gitlab.com/xen-project/people/olafhering
> This should have been a "group" I think, so that I could create a xen.git below.
> Now it is an empty repository. Pushing anything to it fails because it lacks a default branch.
> Undoing the mistake fails as well because the webui lacks a knob to delete this repository.

Actually, it's possible to delete the repo.
Navigate to the repo you want to delete ( https://gitlab.com/xen-project/people/olafhering )
then in the sidebar/menu (hopefully on the left) there is "Setting".
Navigate to "Settings/General", in the "Advanced section" there is
"Delete project", read it all, hopefully it says which repo you want to
delete (olafhering).

At this point, you can probably create a new "subgroup". Navigate to
https://gitlab.com/xen-project/people then click on "New subgroup".

Hopefully, you have your own subgroup now, time to fork Xen!
Navigate to the Xen repo ( https://gitlab.com/xen-project/xen ), then
click "Fork". Choose your new subgroup as "namespace" (project url
section).


Hopefully, those instructions are enough to get you were you want to be.
Otherwise, I think I can do all that if needed.

Cheers,

-- 
Anthony PERARD


  reply	other threads:[~2021-07-16 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  6:54 [PATCH v1] automation: collect log files in subdirectories Olaf Hering
2021-07-08 11:43 ` Andrew Cooper
2021-07-08 11:49   ` Olaf Hering
2021-07-14  7:31   ` Olaf Hering
2021-07-16 14:28     ` Anthony PERARD [this message]
2021-07-16 14:41       ` Olaf Hering
2021-07-20 15:41         ` Anthony PERARD
2021-07-22 16:14           ` Olaf Hering

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=YPGXm9F3OHqLk/ml@perard \
    --to=anthony.perard@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=olaf@aepfle.de \
    --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.