> Dear Matt,
> please see below some additional background on Gerrit that you might find
> useful.
>
> > On 28 Apr 2015, at 16:09, Matt W. Benjamin wrote:
> >
> > Hi,
> >
> > As I mentioned in an IRC discussion, my recollection from when OpenAFS
> > implemented gerrit (also their own installation
> > >> From what I can tell, Frank finds problematic
> > >
> > > 1) a lack in gerrit of a "changeset" concept, plus, apparently
> >
> > It actually exists and is called “topic”. It will be very soon
> > possible as well to merge a whole topic atomically with one click.
>
> I found "topic" mentione
> reply is in the message body. I cut some pieces of your original message
to
> avoid a too long message where information would be diluted.
>
> On 04/24/15 23:59, Frank Filz wrote:
> > 1. Abandon gerrithub, revert to using github branches for review and
> merge.
> > This has a few problems.
> The
Hi (and thanks for the information, I was surprised to see a message
from this mail address ;))
Matt W. Benjamin wrote on Tue, Apr 28, 2015 at 11:22:17AM -0400:
> - "GerritForge Support" wrote:
> > It actually exists and is called “topic”. It will be very soon
> > possible as well to merge a
Hi Matt,
with regards to the NodeDB feature, it is already available on Gerrit on the
version we are currently using on GerritHub.io: just need to be enabled.
We could set-up a test-instance for you guys to try out (e.g. on our Staging
environment: staging.gerrithub.io) and, if you like the feat
Hi,
- "GerritForge Support" wrote:
> >> From what I can tell, Frank finds problematic
> >
> > 1) a lack in gerrit of a "changeset" concept, plus, apparently
>
> It actually exists and is called “topic”. It will be very soon
> possible as well to merge a whole topic atomically with one clic
Hi all,
I've been working on automated testing for all of us today, I believe
more should spend some time on this.
You will notice ganesha-triggers adds Verified +1 sometimes now, this
comes from our jenkins build, it:
1/ will NOT run on all the pushes automatically. Currently, it will
trigger
Dear Matt,
please see below some additional background on Gerrit that you might find
useful.
> On 28 Apr 2015, at 16:09, Matt W. Benjamin wrote:
>
> Hi,
>
> As I mentioned in an IRC discussion, my recollection from when OpenAFS
> implemented gerrit (also their own installation, but not to my
>
Hi,
As I mentioned in an IRC discussion, my recollection from when OpenAFS
implemented gerrit (also their own installation, but not to my
knowledge customized), it was basically mandated that developers
submit "one patch per change."
>From what I can tell, Frank finds problematic
1) a lack in ge
Hi Frank,
reply is in the message body. I cut some pieces of your original message
to avoid a too long message where information would be diluted.
On 04/24/15 23:59, Frank Filz wrote:
> 1. Abandon gerrithub, revert to using github branches for review and merge.
> This has a few problems.
The iss
10 matches
Mail list logo
