Thanks Stefan for the helpful information and I will learn about it.
Yes we need to switch to trunk from master and we wouldn't trigger the Jenkins
on other branches in the current situation.
Regards,
Kai
-Original Message-
From: Stefan Seelmann [mailto:m...@stefan-seelmann.de]
Sent:
I don't quite understand your question. Apparently the codes are in some
module(s), but isn't relevant to the question that whether it should stay in
trunk or a branch. Kadmin-remote is a big new feature that involves significant
new codes and currently it's still in its very early phase,
Hi folks,
I recently added a new module kerby-xdr under the root in kadmin-remote branch,
which made me believe that we will need a better container to contain such
non-kerberos specific things.
Now we have under the root module:
benchmark/
build-tools/
docs/
kerby-asn1/
kerby-backend/
Le 11/01/16 10:18, Zheng, Kai a écrit :
> I don't quite understand your question. Apparently the codes are in some
> module(s), but isn't relevant to the question that whether it should stay in
> trunk or a branch. Kadmin-remote is a big new feature that involves
> significant new codes and
Hi Emmanuel,
Please enjoy and have a wonderful vacation! Will miss you very much for some
discussions. :)
Regards,
Kai
-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com]
Sent: Tuesday, January 12, 2016 3:25 PM
To: Apache Directory Developers List
I thought kadmin remote support discussion should originate in this thread. In
case it's needed again.
Regards,
Kai
-Original Message-
From: Zheng, Kai [mailto:kai.zh...@intel.com]
Sent: Tuesday, December 01, 2015 3:21 PM
To: kerby@directory.apache.org; d...@directory.apache.org
>>At the end of the day, I would say : 'whatever works'.
Yeah, it's my end of the day. Thanks anyway for the discussion, because
discussion is good than none, even not smoothly!
Kindly regards,
Kai
-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com]
Sent: Monday,
Le 11/01/16 12:12, Zheng, Kai a écrit :
>>> your initial message was "kadmin-remote branch is created for the remote
>>> kadmin support work.".
> My message here may be a little simple, but I based on the assumption and
> fact that we have discussed quite much about the feature.
'Quite much'
