►
From YouTube: 2020 08 14 GSoC Git Plugin Performance Project
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
for
today's
meeting
the
first,
the
first
point
of
discussion
is
authentication
with
git
tool
chooser,
so
so
I've
been
working.
So
I
was
on
pr
on
priority.
I
was
working
on
completing
the
github
brand
source,
plugin
extension
implementation,
but
that
is
currently
blocked
on
tests.
I
I
think
liam
is
busy
right
now,
so
we
could
not
have
a
conversation
after
the
last.
A
The
previous
thing
we've
had
so
I
I
I
tried
so
the
issue
I
have
there
is
that
I'm
not
able
to
use
a
mob
github
server
api
server
to
to
stop
data
and
mock
calls
so
that
I
can
write
test
cases.
So
I
have
written
the
test
cases
and
I
am
using
the
already
they
have
a.
They
have
a
class,
a
utility
class
which
provides
a
mock
server
for
such
purposes.
A
But,
despite
extending
them
my
of
the
api,
the
apis
I've
created
for
the
extension,
they
are
still
trying
to
contact
the
github
server
api.
So
that's
creating
an
issue
and
I'm
not
able
to
figure
out
why
that
is
happening.
So
I
I
would
need
his
help
for
that.
A
So
so,
meanwhile,
I
started
working
on
how
I
could
do
the
same
thing
for
git
lab,
and
I
have
created
the
extension
and
while
testing
it
I've
I've
seen
some
issues
which
might
be
might
be
of
concern
for
us.
The
first
is
for
for
git
lab
so
for
github,
sending
the
repository
url
if
you're
not
talking
about
credentials
right
now,
just
a
method
to
get
the
size.
A
Url
was
enough
for
us
sending
that
information
was
enough
for
us
to
get
the
size
of
the
repository,
but
in
case
of
git
lab
so
for
git
lab.
There
is
a
concept
of
a
gitlab
server
and
we
need
to
configure
that
a
user
need
to
configure
that
before
trying
to
open
a
create
a
gitlab
project
organization
for
project
or
multi-brand
project,
so
the
the
problem
with
so
there
is
no
problem
with
configuring.
It
we
we
don't
have.
So.
A
The
problem
with
this
configuration
is
that
gitlab
brand
source
plugin
is
expecting
that
we
know
the
server
name
instead
of
the
server
url
to
instantiate
the
api
instance.
So
to
create
an
api,
it
would
expect
the
server
name
instead
of
the
server
url,
which
I
could
not
understand.
First,
because
I
thought
that
there
should
be
a
way
since
internally,
it
would
use
the
server
url
to
connect.
A
For
gitlab
for
this
configuration-
and
so
that's
that's
something
we
have
to
think
about
also
with
gitlab
what
I've
seen
in
terms
of
now,
let's
come
to
authentication
with
authentication.
We
don't
have
to
worry
in
gitlab.
They
do
that
themselves.
So
what
happens
is
if
we
provide
the
server
name?
If
you
can
see
in
the
configuration
here,
let
me
zoom
a
little
bit.
The
user
would
add
the
credentials
and
a
secret
token,
so
it
requires
a
personal
token,
a
gitlab
personal
token.
A
A
So
so
that's
that's
a
great
thing
in
terms
of
in
terms
of
sending
when
we
were
confused,
how
to
send
the
credentials
and
then
I
looked
I
I
went
back
to
get
her
brand
source
plugin
to
see
if,
since
github
brand
source
plugin,
maybe
not,
we
don't
have
to
configure.
A
I
think
in
the
same
way
create
a
configuration.
In
the
same
way,
we
would
have
a
user
stored
configuration
for
the
project
in
the
github
branchos
plugin
as
well,
so
the
github
transfers
plugin
would
have
the
credentials
it
should.
It
may
have
a
method
where
it
would
not
need
the
credentials
to
create
an
api
instance.
I
haven't
found
one.
A
I
will
look
more
and
I'll
ask
liam
if
there's
a
way,
but
since
it's
possible
in
git
lab,
I'm
I'm
just
wondering
if
it's
if
it's
something
which
is
also
possible
with
github
brand
source
plugin
or
not,
I
I
was
checking,
but
I
could
not
find
the
method
with
the
name
thing.
What
I
want
to
ask
is
that,
since
this
is
a
global
configuration
page,
how
can
we
access
this?
If,
if
we
were,
if
we
were
to
send
the
name
instead
of
the
url,
how
would
we
access
this
information
is?
A
Is
this
stored,
so
this
is
this
is
captured
by
the
descriptor
class
of
the
particular
plugin,
or
is
this
stored
in
the
environment?
Variable.
B
A
No,
no
justin,
I'm
talking
about
so
the
github,
so
the
git
lab
transfers
plugin
expects
that
we
know
the
server
name
of
the
gitlab
server
when
we
are
asking
for
any
details.
A
So
so
we
would
know
the
server
url
that
that
we
can
extract
from
the
repository
url,
but
the
server
name
is
something
which
is
id
which
is
unique
for
this
configuration
it's
used
by
the
plugin.
So
yes,
yes,
mark.
C
C
The
url
to
a
repository
is
clearly
the
way
to
identify
a
repository.
Why
should
I
have
to
know
a
display
name
that
a
user
assigned
to
one
of
potentially
many
get
lab
servers
that
are
connected
to
this
jenkins
instance,
but
party
che
probably
will
give
very
good
reasons.
Why?
And
I
just
don't
know
how
you're
going
to
fit
it
into
the
api,
because
a
gitlab
server
name
probably
isn't
needed
for
giddy
or
for
bitbucket
or
for
github.
B
C
Right
right
and
no
dispute
that
you
can
run
it
and
bitbucket
right,
no
dispute
that
I
could
have
multiple
giddy
servers
and
multiple
multiple
of
any
server
right.
Absolutely
it's
that!
Even
if
I
have
multiple
of
them,
the
you
are
the
server
you,
the
the
ho.
The
url
to
the
repository
is
still
the
unique
identifier
for
the
repository
and
yeah
so
having
needing
to
know
the
name
of
of
of
now.
Maybe
maybe
there
is
such
a
concept
in
github
as
well,
and
we
should
gather
it
everywhere.
I
I
haven't
it's.
B
Look
at
one
two,
but
I
mean
I
think
I
think
the
github
branch
source
plugin
should
know
this.
For
that
item,
though
it
should
have.
B
Like
you
have
to
configure
that
like
that
that
that
particular
particular
multi-branch
project
has
to
be
configured
with
the
server,
so
you've
got
a
hook
there.
I
was
a
mentor
on
the
gitlab
branch
source
plugin.
Oh.
B
Yeah
but
party
rocked
that
so
like
and
I
had
some
other
stuff
going
on
personally,
so
there
may
be
things
that
we
do
need
to
hit
him
up
on,
so
I'm
totally
okay,
so.
B
Of
information,
not
a
let's
not
talk
about
each
year,.
B
B
Sorry,
I'm
marketing
my
own
little
plug-in.
A
Yes,
my
question
is
that
if
I
have
the
repository
url,
even
if
it's
a
private
server
and
the
user
has
entered
the
repository
url,
that
should
be
enough
to
get
me
that
information
right.
Why
would
I
need
to
know
the
server
name
for
for
to
to
get
the
size
of
the
repository?
If
I
have
the
repository
you
wanted.
B
So
the
branch
source
plugins
have
those
as
two
separate
pieces
of
information.
You
don't
just
plug
in
the
the
repo
url.
What
you
do
is
you
plug
in
which
github
server
you
want
and
then
what
owner?
That
is
if
you've
got
like,
if
you're
trying
to
do
it
on
an
org
level,
you
do
what
owner
it
is,
and
then
it's
going
to
scan
everything
underneath
that
org
for,
like
a
github
org,
find
all
the
repositories
that
qualify
create
projects
for
those
and
then
those
each
have
things
actually
maybe
in
under
the
projects.
B
C
So
isn't:
isn't
the
challenge
then,
for
for
rishabh
is
that
in
the
context
where
he's
running,
how
does
how
does
he
communicate
back
to
gitlab
or
how
do
you?
How
does
he
determine
which
api
endpoint
or
which,
which
get
lab
name,
is
being
used,
because
I
assume
you're
you've
got
an
item
context
right,
rishab.
C
There
is
an
item
context
and
that
thing
could
therefore
be
part
of
a
job
or
is
a
job
that
is
running
inside
of
a
multi-branch
pipeline
or
inside
of
an
organization
folder.
But
now
you
need.
You
need
information
to
pass
to
the
gitlab
server,
which
is
somehow
all
the
way
up
at
that
organization.
Folder
right
that
you
need
to
know
which
gitlab
api
endpoint
they
should
use
and
one
way
of
identifying
the
api
endpoint
is
by
this
display
name.
A
I
I
did
ask
him
this
question.
I
think
an
hour
back
on
the
guitar
channel,
but
I
think
we,
if
we
can
have
a
conversation
with
him
here,
then
that
would
be
great.
C
Well,
and-
and
it
may
be,
that
we
need
to
do
some
if,
if
parachute
doesn't
respond
by
say
monday,
we
can
probably
ask
questions
to
the
maintainer
of
the
giddy
plug-in
stephen
connolly
or
to
the
maintainers
of
the
scm
api
like
jesse,
glick
and
devin
nussbaum
and
liam
newman,
because
I
think
each
of
those
people
devin,
maybe
not
but
jesse
glick-
certainly
knows
the
scm
api
and
steven
created
the
sem
api.
C
A
Okay,
so
so
I
think,
what's
interesting.
B
Is
that
the
github
plugin,
the
github
plugin,
is
what
has
your
repository
url
in
a
github
branch
source?
A
B
And
then,
if
you
look
at
a
repo
view,
you
don't
see
like
that
project
doesn't
have
any
awareness
that
it's
part
of
a
get
a
branch
source.
It
has
a
github.
B
Well,
it
does
know
that
sorry,
it
has
a
branch
sources
portion.
You
can
kind
of
see
some
of
this
stuff
in
the
ui
like
how
plugins
work
together,
because
they'll
have
their
own
like
jelly
labels
and
stuff.
Like
that,
it's
kind
of
interesting
though,
but
anyways
you
can
tell
that
the
github
is
a
github
configuration
that
has
credentials
it
has
the
repository
https
url,
and
then
that
is
what
is
invoking
git
plugin,
I
think
for
github.
I
don't
know
we
can
look
at
gitlab
too,
but
I
can.
B
A
So
I
I
think
from
my
side
I
have
why
I
haven't
explored
this
side-
is
that
I've
always
tried
to
when
I'm
interactively
testing
the
extensions
I've
always
done
it
with
just
installing
these
modified
plugins,
the
github
or
the
gitlab
plugin,
not
configuring
a
multi
branch
project
just
running
a
freestyle
job
for
git
in
and
seeing
if
those
extensions
are
able
to
provide
the
size.
A
So
that
is
why
I
haven't
I've
completely.
I
would
say,
ignored
that
site
that
if
we
have
a
multi
branch
source,
that's
a
github
organization
project
or
a
git
lab
organization
project.
In
that
case,
how
so
in
in
git
lab,
I
was
forced
to
go
to
the
config
global
configurations
and
add
a
server.
Add
a
server
name.
Add
those
details
in
github.
I
did
not
have
to
do
anything
I
my
plugin
was
able
to
with
just
the
repository
url
was
able
to
communicate
the
size
to
me.
C
C
But
the
get
lab
plug-in
is
not,
and
maybe
it's
time
to
say,
ask
the
question
to
potice
and
then
say:
I'm
going
to
go,
try
another
one
or
or
focus
elsewhere,
just
because
it
may
be
that
that
the
gitlab
plug-in
isn't
ready
to
answer
the
question
that
we
want
to
ask
in
the
context
we
want
to
ask
it.
I
hadn't
even
thought
of
the
the
you
described
it
very,
very
well.
A
freestyle
project
doesn't
have
an
organization
folder
or
a
multi-branch
context
to
to
be
able
to
provide
it's
very
good
insight.
A
Yes
mark
so
so
I
think,
since
I
think
we
have
what
two
weeks
now
to
if
you
want
to
release
this
like
these
features
with
the
new
version.
So
so
I
don't
want
to
be
blogged.
I
I
think
I
can
explore
from
my
side
by
creating
a
multi-branch
project
and
then
so
the
best
way
for
me
personally
is
I
debug.
A
I
try
to
debug
the
local
instance
by
attaching
a
maven
debugger,
so
if
I'm
able
to
understand
how
the
interactions
are
working
there,
so
I'll
I'll
try
that
personally,
but
I
I
think
I've
asked
parice
if
he
is
able
to
respond,
maybe
to
get
that
answer
throughout
the
weekend.
That's
okay!
So
so
my
question
is
that,
should
I
move
on
to
the
getty
brand
source,
plugin.
C
A
A
This
thing
I
forgot
actually
throughout
this
discussion-
I
I
remember
that-
is
it
absolutely
necessary
for
us
to
look
at
the
brand
source
plugins
to
get
this
information
for
an
example
right
now
we
are
seeing
that
the
github
plugin
might
be
able
to
provide
us
this
information
as
well.
So
so
is
it
for
so
for
the
other
plugins
as
well.
A
Do
we
absolutely
need
a
brand
source
plugin
to
get
this,
because
when
I
was
thinking
about
get
to
chooser
and
getting
the
size,
I
was
not
thinking
about
the
the
the
layers
on
upon
which
these
brand
source
plugins
depend.
So
now,
as
I've
seen
the
code,
I
understand
that
these
brand
source
plugins
are
implementing
another
plugin
which
wraps
around
the
java
apis
with
for
the
rest
apis.
It
says
the
java
code
for
the
rest
apis
for
maybe
git
lab
or
for
github.
A
We
have
the
github
plugin
I've
seen
that
so
do
we
need
the
brand
source
plugin
because
we
just
need.
We
need
the
size
we're
we're
looking
at
brand
branson's,
because
I
just
I
I
I
did
not
know
that
we
could
do
the
same
thing
with
the
github
plugin.
But
if
we
can
do
the
same
thing
with
the
get
a
plug-in,
why
would
we
need
to
ask
that
question
to
the
branch
source
plugin.
B
Yeah,
so
this
is
actually
clearing
up
some
cobwebs
in
my
mind,
so
you
what
you're
doing
is
actually
a
great
test.
B
This
freestyle
project
approach
is
actually
the
proper
way
because
you
actually
don't
care
about
multi-branch
projects,
because
that
already
gives
you
the
cash
right
so
between
what
you've
already
done,
like
the
great
work
you've
already
done,
and
then
that,
like
I
think
your
test
is
going
well
in
terms
of
like
freestyle
project,
a
branch
source
plug-in
generally
just
sets
up
a
project
for
you
and
sets
up
a
branch
source
with
that
provider's
plug-in
stuff.
B
So
I
think
you're
going
to
be
able
to
accomplish
this
in,
and
I
I
do
recall
that
in
the
gitlab
project
we
were
also
trying
to
kind
of
take
advantage
of
a
lot
of
the
success
that
the
github
branch
source,
plug-in
and
github
plug-in
suite
in
general
was
doing
so.
I
think
that
pattern's
going
to
be
fairly
consistent
across
the
way-
and
I
do
remember
that
we,
I
think
pariche
had
worked
with
jesse
and
some
other
folks
and
probably
stephen
all
yeah.
I
think
stephen
and
jesse
on
some
of
those
so
yeah.
B
C
C
It
just
happens
that
the
branch
sources
always
have
to
do
a
rest,
api
implementation
and
therefore
they
are
a
likely
candidate
to
have
a
rest
api
implementation
so
but
you're
absolutely
right.
If
there's
a
if
there's
a
a
plug-in
that
provides
an
api
to
a
provider
who
would
answer
the
question
about
size,
then
that
plug-in
is
a
candidate
to
implement
this
extension.
A
Yes
and
okay,
so
I
think
I
will-
and
what
I
also
want
to
ask,
is
that
so
it's
not
necessary
that
each
brand
source
plugin
would
have
a
plugin
depending
on
a
plugin
which
is
implementing
the
apis
it.
It
may
be
possible
that
those
apis
are
implemented
within
the
brancos
plugin.
C
A
C
C
B
B
There
may
not
be
an
api
plug-in,
but
there's
a
git
lab
plug-in
itself
which
made
you
like.
Sometimes
they
split
those
out
too
okay,
but
yeah.
There's
a
gitlab
plugin
too,
which
you
should
definitely
take
a
look
at.
A
B
A
Require
the
server
name,
we've
discussed
it.
I
I
had
one
more
thing
in
my
mind.
I
don't
remember.
Oh
yes,
so
with
git
lab
one
more
thing
that
I've
seen
is
that
so
git
lab
for
gitlab
repository.
If
we
github
we
have
repositories
and
in
gitlab
I
think
the
equivalent
is
a
project
and
so
for
a
project.
We
have
the
code
base
in
it
and-
and
I
think
the
ci
cd
is.
It
has
multiple
things.
A
It's
it's
a
broader
definition
and
repositories
so
so
to
get
the
size
of
the
of
of
the
code
base
or
the
objects
we
have
it
if
it
uses
a
separate
extension
of
the
api,
which
is
called,
which
basically
adds
a
statistics
boolean
to
it,
the
ap
the
whole
api
to
get
that
information
and
what
I'm
seeing.
So
we
have
roles
in
the
gitlab
right
for
permissions.
We
have
roles,
we
have
the
owner,
we
have
developed
developers.
I
I
I
think
I
have
opened
it.
We
have
guest
reporter
developer,
maintainer
and
owner.
A
A
That
is
the
size
of
the
repository
the
user
should
be
the
owner
of
that
repository,
which
then
seems
I
think
we
cannot
do
anything
about
it
if
git
lab
has
decided
that,
but
then
it
narrows
down
our
scope,
I
think,
in
a
in
a
huge
way,
because
our
developer
developer
maintain
a
reporter
or
at
any
level,
will
not
be
able
to
get
that
information,
but
for
a
certain
type
of
role
which
which,
which
is,
I
think,
is
an
issue.
A
So
I
I
did
check
if,
if
this
is
true
or
not
new
project
statistics,
so
here
it
does
say
that
the
developer,
the
maintainer
and
the
owner-
all
those
three
can
see
this.
A
But
strangely
enough,
when
I
go
to
the
project
api,
which
is
the
git
lab
done
source,
I
think
this
is
the
gitlab
plugin
only
where
the
instances,
the
gitlab
api
instance
is
being
created
using
this
class,
so
there
it
says
that
to
get
a
specific
project
which
is
owned
by
the
authenticated
user.
A
That
is
how
we
can
get
the
project
statistics,
and
this
is
how
we
can
get
the
size.
A
So
so,
with
git
lab
I
haven't
tested,
I
wrote
the
extension
I
and
I
could
not
test
it
test
it
in
the
sense
that
I
did
not
put
it
in
a
local
ins.
I
did
put
it
in
a
local
instrument,
but
I
was
not
able
to
get
the
size.
A
I
was
having
some
issues
with
it,
so
I
I
think
I
need
to
make
sure
that
make
sure
that
that
we
may
not
be
able
to
and
not
everyone
may
be
able
to
get
the
size
of
the
project
or
the
repository
so
and
if
it's,
if
it's
just
the
owner,
then
that
might
be
that
might
limit
our
use
case,
but
it
I
I
don't
think
it
there
is
something
we
can
do
about
it.
B
Yeah,
that
might
be
something
that
you
need
to
end
up
documenting
or
something
like
that.
If
it's,
if
it's
a
specific
permission
that
needs
to
be
set
up
for
that
token,
that
you
wouldn't
already
get
by
just
simply
setting
up
a
gitlab
project.
A
B
Okay,
actually
so
to
go
back
to
the
caching
thing,
if
you
have
a
branch
source,
no
matter
what
you
have
a
cache
right.
A
A
C
With
that
statement,
I'm
just
trying
to
understand
how
we
communicate,
how
does
the
user
who's?
How
does
the
user,
who
defines
a
freestyle
job,
tell
us
tell
tell
the
plugin
which
get
lab
servers
being
used
behind
this
url
and
I
think
right
now,
the
answer
is
they
don't
there's
no
facility
for
produced.
B
C
C
Yeah,
I
don't
think
that
I
don't
think
those
higher
level
providers
implement
at
the
freestyle
project
level-
oh
yeah,
you're
right,
but
but
so
so
we're
back
to
the
it
may
be
that
the
only
fallback
for
a
freestyle
user
is
if
they're,
lucky
and
they've
got
a
job
defined
elsewhere.
That
causes
them
to
have
the
cash
for
that,
because
we
freestyle
has
no
way
to
say.
I
want
to
use
this
gitlab
server
or
I
want
to
use
this,
and-
and
I
don't
it
feels
like
that-
would
be
huge-
a
huge
scope
creep
for
me.
C
If
you
said,
oh,
I'm
going
to
add
that
so
that
anytime,
you
add
a
git
project,
you
need
to
also
optionally
choose
or
add
git
scm.
You
need
option
to
choose
the
higher
level
provider
that
just
that.
I
that's
that's
an
awful
lot
of
addition
in
a
spot
where
we're
just
trying
to
get
a
guess
of
how
big
the
repository
is.
A
That,
yes,
okay,
so,
okay,
I
think
that's
what
I
have
to
do
right
now,
and
the
last
thing
I
wanted
to
discuss
was
the
release
plan
for
what
we,
so,
how
do
we
want
to
so
with
the
get
tool?
A
Chooser
pr,
I
think
we
mark
I've,
seen
your
comments
and
I
just
have
to
I've
fixed
the
test,
the
test
case,
which
was
failing
on
windows,
and
so
I
think
after
that,
what
all
do
we
need
for
the
get
tool,
chooser
or
maybe
should
okay,
we
have
to
wait
till
we
do
not
find
a
consolidated
way
to
communicate
with
the
extension
part
of
it.
I
think
right.
A
So
I
think,
then
the
get
tool
user
is
blocked
until
unless
we
so
I
I
have
to
look
at
the
github
plugin
and
the
git
lab
like
in
the
api
plugins
first,
I
think.
C
So
for
me,
I
think
that's
already
an
indication
that
we
should
press
forward
using
that,
except
that,
okay
for
now
gitlab,
we
don't
know
how
git
lab
will
provide
that
information,
but
we
do
know
how
github
can
provide
it.
C
A
Okay,
so
in
that
case,
if
we
so
if
you're
looking
so
we
have
the
github
github
brand
source,
plugin
implementation
and
once
the
test
cases
that
problem
is
fixed,
we
would
have
that
we
are
merged,
and
once
we
have
that
I
so
I
want
to
understand.
How
would
we
do
this?
Would
we
merge
git
tool
chooser
first,
or
would
we
wait
for
the
get
a
brand
source
plugin
to
do
that,
so
that
we
know
that?
Okay,
one?
There
is
one
plugin
which
is
supporting
the
tool
chooser.
C
A
A
I
haven't
added
the
instantiations.
I
haven't
added
the
get
to
chooser
at
every
point,
because
I've
always
I'm
stuck
the
authentication
part
or
the
extension.
So
so
what
I
want
to
ask
is
do
I
should
I
add
that
within
this
pr
or
first
should
we
add,
get
to
chooser
as
a
function
as
a
as
a
separate,
independent
class
within
the
git
plugin,
and
then
we
add,
get
to
choose
in
a
separate
pr.
We
add
the
git
tool
chooser
at
places
where
we
would
need
to
make
the
decision
of
recommending
an
implementation.
C
A
Okay,
so,
okay,
so
so
I
have
done
done
so.
I
have
instantiated
the
get
tool
chooser
in
the
git
scm,
the
checkout
step
in
this
pr,
the
pr
937,
which
is,
which
is
a
branch
taken
from
the
the
current
get
to
user
branch,
is
it
supports
the
unsupported
command
functionality
to
give
a
better
recommendation
in
terms
of
jigget.
So
I
think
I
would
add,
all
of
those
in
this
pr
and
then
we
could
merge
it
with
git
tool
chooser
or
I'm
not
sure.
How
should
I
do
this.
C
A
C
A
I
would,
I
would
add,
I
would
add
those
just
yes,
we
have
more
tests
in
931,
we
don't
have
those
in
937.,
so
937
was
just
to.
I
created
it
for
just
the
unsupported
command
feature,
and
then
I
thought
that
we
would
merge
it
and
and
then
go
forward.
It's
just
create
more
confusion.
For
me,
I
think.
C
A
Yes,
so
I
think
the
point
is
that
we
we
want
a
single
pr
where
we
have
the
workable
get
to
chooser
for
the
gift
plugin
right.
C
Right
now
now
you
could,
you
could
optionally,
take
everything,
take
the
things
that
you've
learned
from
937
and
pull
them
into
931,
whichever
one
you
feel
is
it
just
as
I
was
reviewing
the
two
of
them
last
night
I
and
I
saw
common
code
between
them
and
thought.
Oh
he's
been
working
one
off
the
other.
That's
great!
I
assume
we
merge
one
of
the
two
and
you
get
to
pick,
which
one
is
better
for
you.
A
Okay,
I
I
think
since
931
has
the
latest
design
changes
937
doesn't
so
I
would
copy
out
the
editions
of
937
to
931.,
yeah,
yeah
and
I'll.
Do
that.
A
B
C
There
are
all
sorts
of
get
power
tools
to
help
you
in
reshub.
There's
cherry
pick,
there's
rebase.
There
are
all
sorts
of
great
things
that
and
and
every
one
of
those
could
be
a
terror
cause
you
terrible
wounds
that
are
nearly
fatal
to
your
repository.
So,
yes,
git
is
a
great
power
tool
and
there
are
times
it
would
be
happy
to
cut
your
foot
off.
A
I
I
think
this
is
it
then,
for
that
so
for
us
to
release
get
tool
chooser,
I
we.
We
need
to
merge
this
one
single
pr
with
the
workable
solution,
and
apparently
I
I
will
be.
I
am
working
on
looking
on
the
extensions
and
I
think
that's
that's
it
for
now
and
then
I
I
need
mark.
I
we
need
to
figure
out
a
way
to
either
profile
the
instance
where
you
have
a
lot
of
jobs
or
we
could.
You
were
talking
about
adding
a
time
stamp
which
could
get.
A
C
You
you
are
welcome
to
attempt
it.
I
am
happy
to
give
you
full
access.
I
have
never
tried
to
profile
inside
a
docker
image
that
is
running
something
as
large
as
my
there
are
only
4
000
jobs,
on
my
on
my
ci
instance,
and
of
those
4
000
jobs.
There's
a
reason
that
the
computer
that
hosts
it
has
32
gigabytes
of
memory,
and
so
so
I
worry
that
that
the
profiler
may
may
cause.
C
You
surprises
that
you
didn't
really
want
to
have
to
manage,
whereas
timestamps
reporting
to
a
file
to
the
log
file
are
pretty
predictable,
you
know
they
are.
They
are
certainly
aren't
as
fine-grained
or
as
accurate
as
as
profiling,
but
they
can
give
us
course
enough
for
this
kind
of
this
kind
of
assessment.