ng0 skribis:
> David Craven writes:
>
>>> 1. Our commit history is not full of merges of tiny branches, which is
>>> what GitHub (and I thought Gitlab) encourages.
>>
>> Yes, that is right. But as I mentioned in a different thread, there
>> are many projects where the maintainers agree to no
> Also Kallithea does have an issues tracker on their roadmap, but it is
> not being worked on at the moment (I asked in their irc channel).
>
> At the same time I'm working on darcs, gogs and a go build-system and
> all kinds of other things. From packaging I don't know what gitlab
> wants as I ha
Ben Woodcroft writes:
> Hi ng0,
>
> On 06/09/16 09:17, ng0 wrote:
>>> Who wants to take on this? Any volunteers?
>> On second note, my server is intentionally very minimal, so I have to
>> look at if gitlab will be fully functional (email etc).
>
> Did you have any success working with Kallithea?
Andreas Enge writes:
> Hello,
>
> using debbugs corresponds to a suggestion I made a while ago, so I am
> obviously in favour of it...
>
> On Sun, Sep 04, 2016 at 10:37:02AM +0800, Alex Vong wrote:
>> > I think it would make sense to have the one bug report for the "target
>> > package" and then
Hi ng0,
On 06/09/16 09:17, ng0 wrote:
Who wants to take on this? Any volunteers?
On second note, my server is intentionally very minimal, so I have to
look at if gitlab will be fully functional (email etc).
Did you have any success working with Kallithea? It seems on the face of
it to be the
> How would we proceed with this?
I think that someone needs to write a service for gitlab first, since
we probably want to deploy it using guixsd ;) Then probably Ludo will
take over this. To give this a fair shot it has to be at least as much
effort to revert to the old way of things as to conti
> Who wants to take on this? Any volunteers?
On second note, my server is intentionally very minimal, so I have to
look at if gitlab will be fully functional (email etc).
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
David Craven writes:
>> 1. Our commit history is not full of merges of tiny branches, which is
>> what GitHub (and I thought Gitlab) encourages.
>
> Yes, that is right. But as I mentioned in a different thread, there
> are many projects where the maintainers agree to not use the merge
> butto
> 1. Our commit history is not full of merges of tiny branches, which is
> what GitHub (and I thought Gitlab) encourages.
Yes, that is right. But as I mentioned in a different thread, there
are many projects where the maintainers agree to not use the merge
button because of this. Since we are
Hello!
Alex Kost skribis:
> David Craven (2016-09-04 20:09 +0300) wrote:
>
>> Why is the gitlab not including the rebase feature a deal breaker?
>
> I'm wondering too.
>
>> It's open source, so disabling the merge button in the ui isn't a big
>> deal. We can continue using git push like we've be
David Craven (2016-09-04 20:09 +0300) wrote:
> Why is the gitlab not including the rebase feature a deal breaker?
I'm wondering too.
> It's open source, so disabling the merge button in the ui isn't a big
> deal. We can continue using git push like we've been doing so far...
I also don't see a
Why is the gitlab not including the rebase feature a deal breaker?
It's open source, so disabling the merge button in the ui isn't a big
deal. We can continue using git push like we've been doing so far...
Also I've mentioned previously - why not gogs - but I'm ok with either.
Resend because somehow this ended up being send from my unsubscribed
address:
ng0 writes:
> Andreas Enge writes:
>
>> Hello,
>>
>> using debbugs corresponds to a suggestion I made a while ago, so I am
>> obviously in favour of it...
>>
>> On Sun, Sep 04, 2016 at 10:37:02AM +0800, Alex Vong wrot
Andreas Enge writes:
> Hello,
>
> using debbugs corresponds to a suggestion I made a while ago, so I am
> obviously in favour of it...
>
> On Sun, Sep 04, 2016 at 10:37:02AM +0800, Alex Vong wrote:
>> > I think it would make sense to have the one bug report for the "target
>> > package" and then
Hello,
using debbugs corresponds to a suggestion I made a while ago, so I am
obviously in favour of it...
On Sun, Sep 04, 2016 at 10:37:02AM +0800, Alex Vong wrote:
> > I think it would make sense to have the one bug report for the "target
> > package" and then all the packages that get pulled in
Efraim Flashner writes:
> On Fri, Sep 02, 2016 at 02:39:12PM +0200, Ludovic Courtès wrote:
>> Hi Alex!
>>
>> Alex Vong skribis:
>>
>> > While it may not be as user-friendly as web-based bug tracker these
>> > days, I think the Debian bug tracking system is still better than our
>> > current ap
l...@gnu.org (Ludovic Courtès) writes:
> Alex Vong skribis:
>
>> Ricardo Wurmus writes:
>>
>>> Ludovic Courtès writes:
>>>
I suppose it wouldn’t handle patch series very well though, would it?
Or people would have to send the “cover letter” of the series first, and
then send the
On Fri, Sep 02, 2016 at 02:39:12PM +0200, Ludovic Courtès wrote:
> Hi Alex!
>
> Alex Vong skribis:
>
> > While it may not be as user-friendly as web-based bug tracker these
> > days, I think the Debian bug tracking system is still better than our
> > current approach. In Debian, everything is a
Alex Vong skribis:
> Ricardo Wurmus writes:
>
>> Ludovic Courtès writes:
>>
>>> I suppose it wouldn’t handle patch series very well though, would it?
>>> Or people would have to send the “cover letter” of the series first, and
>>> then send the rest to n...@debbugs.gnu.org once a number has bee
Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> I suppose it wouldn’t handle patch series very well though, would it?
>> Or people would have to send the “cover letter” of the series first, and
>> then send the rest to n...@debbugs.gnu.org once a number has been
>> assigned?
>
> Or could w
Ludovic Courtès writes:
> I suppose it wouldn’t handle patch series very well though, would it?
> Or people would have to send the “cover letter” of the series first, and
> then send the rest to n...@debbugs.gnu.org once a number has been
> assigned?
Or could we have a bug per module? Then the
21 matches
Mail list logo
