Would you mind if I wrote up a proposed alternate that doesn't use rebase
and eliminate fast forwards? Yes, it will mean there is an extra 'useless'
commit... which I don't actually always find useless, but I think it
simpler. Then let's just discuss.
Yes please.
I am not trying to assert my opinion over yours and you clearly did a lot
of work to get us here. Just trying to offer some approaches since there
is clearly confusion among the people using it, and I think some of it, in
my opinion, is that we are showing something more complicated than is
strictly necessary and I don't see the advantages outweighing the
disadvantages.
No problem, it just a talk, you and me want the best for Apache Flex.
I would love to work on this with you if you are interested
Sure.
Cheers,
-Fred
-----Message d'origine-----
From: Michael A. Labriola
Sent: Sunday, March 24, 2013 1:18 AM
To: dev@flex.apache.org
Subject: RE: [Git/Wiki] please review the proposed workflow and comment
As I said before, at least at the beginning, I wouldn't like committers new
in git have a chance to run into problems and in the same time I wouldn't
like they have to think to much about what should he use in that
>situation, that's the reason why I created this workflow and for sure if
there is a better way to achieve this, amen.
Would you mind if I wrote up a proposed alternate that doesn't use rebase
and eliminate fast forwards? Yes, it will mean there is an extra 'useless'
commit... which I don't actually always find useless, but I think it
simpler. Then let's just discuss.
I am not trying to assert my opinion over yours and you clearly did a lot of
work to get us here. Just trying to offer some approaches since there is
clearly confusion among the people using it, and I think some of it, in my
opinion, is that we are showing something more complicated than is strictly
necessary and I don't see the advantages outweighing the disadvantages.
I would love to work on this with you if you are interested,
Mike
