Lewis, did you or anyone else feel that you were pushed to git?
While your story has a bit of @infra-specific business to it, the majority
of it and flex's seem to be composed of 'we heard that git was cool, so we
moved to it, and we stepped on a rake.'
Personally, I wouldn't recommend that any c
Hi,
(removed board@ and dev@flex from my reply)
I've watched this thread with a keen sense of interest.
I would like to point out that we (the Any23 community) have more or less
experienced the exact same as the flex guys.
The build was broken as git binaries are not available on solaris slaves
for
Ross, agreed. A list of potential "gotchas" would be sensible!
On 27 April 2013 17:26, Ross Gardler wrote:
> Let me repeat again that the value I see in the Flex report is that it
> identifies some issues that projects moving to git should consider and plan
> for. This will make other projects
Let me repeat again that the value I see in the Flex report is that it
identifies some issues that projects moving to git should consider and plan
for. This will make other projects migrations smoother.
Sent from a mobile device, please excuse mistakes and brevity
On 26 Apr 2013 18:35, "Luciano Re
I interpreted Luciano's -1 as a general "I am not in favour of this
proposal", which seems like a perfectly valid use. Even if it were being
cast _as_ a veto on some code change or other, I still think it would be
valid, as it comes with justification. (That other people might disagree
with that ju
Luciano Resende wrote on Fri, Apr 26, 2013 at 10:34:39 -0700:
> -1 for using Apache Flex's bad experience, as a concrete example, as this
> might give the wrong perception about Git at Apache.
Sorry, invalid veto. You can't veto people from citing a datapoint
because it's not favourable to one si
