Hi, can the pollster gather the results and move the ball forward? :-)
Gary
On Thu, May 26, 2016 at 5:09 PM, Christopher wrote:
> +1 for git everywhere
>
> On Thu, May 26, 2016 at 5:14 PM Jochen Wiedmann >
> wrote:
>
> > +1 (for all components)
> >
> > Jochen
> >
> >
> > On Thu, May 26, 2016 a
Hi.
Thanks for willing to participate, but the "master" branch should be
modified only by merging the "develop" into it (before preparing a
release).
Cf. rationale in "doc/development/development.howto.txt" (in the
"develop" branch).
Regards,
Gilles
On Sun, 29 May 2016 21:28:11 + (UTC), db
Hi Dave.
Please stop performing changes on the "master" branch!
[See also my other mail.]
Except for trivial modifications (e.g. typo in Javadoc), it was
customary
to file a JIRA report to link to the commit.
A bunch of (even fairly trivial) modifications could be the object of
a JIRA report
ok, apologies. sorry
On 05/29/2016 05:47 PM, Gilles wrote:
Hi Dave.
Please stop performing changes on the "master" branch!
[See also my other mail.]
Except for trivial modifications (e.g. typo in Javadoc), it was customary
to file a JIRA report to link to the commit.
A bunch of (even fairly t
+1
On Wed, May 25, 2016 at 4:43 PM Bernd Eckenfels
wrote:
> Hello,
>
> I would like to be able to use Git with the Apache Commons VFS repo. As
> we agreed upon I call out the intention to do this and ask you for your
> oppinion.
>
> Now that we have the 2.1 release out of the way the switch wont
