* Paul Wise:
> On Sun, Jul 19, 2015 at 5:49 PM, Florian Weimer wrote:
>
>> I don't quite understand this criticism. Surely direct write access
>> to the repository always needs some sort of authentication step?
>
> Not sure about for http/https/ssh but the git protocol allows for
> anonymous push
On Sun, Jul 19, 2015 at 5:49 PM, Florian Weimer wrote:
> I don't quite understand this criticism. Surely direct write access
> to the repository always needs some sort of authentication step?
Not sure about for http/https/ssh but the git protocol allows for
anonymous push access and git-daemon s
* Ondřej Surý:
> Also it still doesn't solve the issue the quarrel here is about - you
> still need some account - in this case a local GitLab instance account
> (well, Alioth could be used if that's in LDAP) to contribute.
I don't quite understand this criticism. Surely direct write access
to t
On Mon, Apr 20, 2015 at 03:06:04PM +0200, Ondřej Surý wrote:
> On Mon, Apr 20, 2015, at 02:09, Brian May wrote:
> > I have never actually used GitLab, so I can't actually comment on how
> > good it is...
>
> Perhaps you should, before you start suggesting thing based on
> GitLab... ;-)
>
> Anyway
On Mon, Apr 20, 2015, at 02:09, Brian May wrote:
> I have never actually used GitLab, so I can't actually comment on how
> good it is...
Perhaps you should, before you start suggesting thing based on
GitLab... ;-)
Anyway - GitLab is quite good these days and it has matured[1], but it's
a typical
Russ Allbery writes:
> It's a UI. The UI is really nice. That's why people use it. But
> lock-in implies more than a really nice UI that people use because
> it's superior.
By lock-in I'm implying vendor lock-in: the customer or user is unable
to switch away from the vendor's service without sig
On Mon, 20 Apr 2015 at 00:19 Ben Finney wrote:
> This is quite frustrating. There's some serious equivocating by GitHub
> apologists in this discussion:
It GitHub better then the open source GitLab?
If the answer is Yes, is there any obstacles to trying to improve GitLab so
it does what we wan
On 20 April 2015 at 02:18, Ben Finney wrote:
> Robert Collins writes:
>
>> Have you used github? If not you should: the best position to critique
>> a system from is one of familiarity.
>
> If I were to critique only the effects GitHub has for the individual who
> uses it, that would be a valid p
On Sun, Apr 19, 2015 at 10:27:01AM -0700, Russ Allbery wrote:
> The repositories and Git management are the very nice features of GitHub,
> and there's nothing there data-wise you can't pretty trivially extract.
> It's just a very nice UI.
In fact, joeyh wrote a nice tool[0] that will extract all
Ben Finney writes:
> We're told that GitHub has a raft of features that make it superior,
> until it's pointed out that those features are GitHub-specific and
> incompatible with collaborators from outside; then, conveniently, the
> specialness of those features dwindles to insignificance because
❦ 20 avril 2015 00:18 +1000, Ben Finney :
> Likewise, as an external party Alice can collaborate via ‘git
> send-email’ or ‘git request-pull’ on an equal footing with any other
> repo (including GitHub repos). But Bob, having chosen GitHub's
> proprietary pull requests as an essential part of hi
Neil Williams writes:
> On Sun, 19 Apr 2015 19:00:33 +1000
> Ben Finney wrote:
>
> > How can a collaborator Alice, with no GitHub account, get the pull
> > request?
>
> Public github repositories do not need a github account to clone.
This is quite frustrating. There's some serious equivocating
On Sun, 19 Apr 2015 19:00:33 +1000
Ben Finney wrote:
> Neil Williams writes:
>
> > On Sat, 18 Apr 2015 17:55:17 +1000
> > Ben Finney wrote:
> >
> > > GitHub's pull request feature is proprietary to GitHub, it can
> > > only work between repositories hosted inside the GitHub silo, and
> > > any
❦ 19 avril 2015 19:00 +1000, Ben Finney :
>> The pull request exists on github, fine.
>
> How can a collaborator Alice, with no GitHub account, get the pull
> request?
Take a random PR:
https://github.com/twbs/bootstrap/pull/16258
Append ".patch" to get the patch:
curl https://github.com/twb
On 19 April 2015 at 21:00, Ben Finney wrote:
> Neil Williams writes:
>
>> On Sat, 18 Apr 2015 17:55:17 +1000
>> Ben Finney wrote:
>>
>> > GitHub's pull request feature is proprietary to GitHub, it can only
>> > work between repositories hosted inside the GitHub silo, and any
>> > project using t
Neil Williams writes:
> On Sat, 18 Apr 2015 17:55:17 +1000
> Ben Finney wrote:
>
> > GitHub's pull request feature is proprietary to GitHub, it can only
> > work between repositories hosted inside the GitHub silo, and any
> > project using that feature is thereby locking its workflow to the
> >
On Sat, 18 Apr 2015 17:55:17 +1000
Ben Finney wrote:
> Russ Allbery writes:
>
> > Ben Finney writes:
>
> GitHub's pull request feature is proprietary to GitHub, it can only
> work between repositories hosted inside the GitHub silo, and any
> project using that feature is thereby locking its w
17 matches
Mail list logo
