public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: devmanual moved to github
Date: Sun, 12 May 2013 20:22:48 +0200	[thread overview]
Message-ID: <20130512182248.15206.qmail@stuge.se> (raw)
In-Reply-To: <1818351.4idgze6HqD@virtuoso>

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

Theo Chatzimichos wrote:
> > > Another option that looks nice is GitLab.
> > 
> > How does it work? The screenshots look exactly like github.
> 
> Don't ask, just go for it!

That's not very helpful?

I'm happy to expand on my experience with Gerrit, and I'll gladly
answer specific questions if I can.


> It's a few steps to set up, but it's not too bad.

Great! Have you run it in production or in a lab? Did you encounter
any non-obvious issues?


> I agree that github is sucky, but I don't think rejecting GitLab
> just because it looks exactly like Github makes sense.

Where did you get the idea that anyone is rejecting GitLab?

Especially surprising that you think that *I* would reject GitLab,
since I'm not even a developer.

(Comparing github with Java doesn't make much sense.)


> Look at what the application does and how it works first.

Yes indeed, obviously I tried that, but the gitlab.org webpage
doesn't have a lot of information beyond the github-like screenshots.

Hence my question to the list, where perhaps someone can talk about
gitlab based on their experience.

All pointers to better resources are surely appreciated not only by me.


//Peter

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2013-05-12 18:22 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 11:32 [gentoo-dev] devmanual moved to github Markos Chandras
2013-05-12 13:12 ` Rich Freeman
2013-05-12 13:27   ` Peter Stuge
2013-05-12 15:02     ` Ben de Groot
2013-05-12 15:15       ` Markos Chandras
2013-05-12 15:12     ` Diego Elio Pettenò
2013-05-12 15:02   ` [gentoo-dev] " Duncan
2013-05-12 13:15 ` Ulrich Mueller
2013-05-12 15:04   ` Markos Chandras
2013-05-12 15:17     ` Peter Stuge
2013-05-12 15:48     ` Ulrich Mueller
2013-05-12 15:54       ` Markos Chandras
2013-05-12 16:08         ` Rich Freeman
2013-05-12 16:12           ` Michael Palimaka
2013-05-14 15:44           ` William Hubbs
2013-05-14 17:51             ` Rich Freeman
2013-05-12 16:55         ` Ulrich Mueller
2013-05-12 16:04       ` Mike Gilbert
2013-05-12 17:20     ` Peter Stuge
2013-05-12 17:32       ` Michael Palimaka
2013-05-12 18:24         ` Peter Stuge
2013-05-12 18:31           ` Michael Palimaka
2013-05-12 22:12           ` Alexander Berntsen
2013-05-12 22:21             ` Peter Stuge
2013-05-12 22:24               ` Alexander Berntsen
2013-05-12 22:37                 ` Peter Stuge
2013-05-13  7:09                   ` Alexander Berntsen
2013-05-12 22:38                 ` W. Trevor King
2013-05-13  6:32                 ` Ralph Sennhauser
2013-05-13  7:07                   ` Alexander Berntsen
2013-05-13  7:40                     ` Ralph Sennhauser
2013-05-13  7:47                       ` Alexander Berntsen
2013-05-13 13:28                   ` Ciaran McCreesh
2013-05-14 15:55               ` William Hubbs
2013-05-13 12:38             ` Greg KH
2013-05-13 12:42               ` Alexander Berntsen
2013-05-13 21:59                 ` Duncan
2013-05-12 17:33       ` Theo Chatzimichos
2013-05-12 18:22         ` Peter Stuge [this message]
2013-05-12 19:18       ` [gentoo-dev] GitLab Feature-Set / Was: " sascha-ml
2013-05-14 13:59         ` Rich Freeman
2013-05-14 14:19           ` Peter Stuge
2013-05-14 14:40             ` Rich Freeman
2013-05-13  3:38     ` [gentoo-dev] " Arun Raghavan
2013-05-12 15:13   ` Richard Yao
2013-05-12 15:38     ` Ulrich Mueller

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=20130512182248.15206.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=gentoo-dev@lists.gentoo.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