lugable, is that a hard requirement
that will be added to the spec? or just a possibility?
--
Darragh Bailey
"Nothing is foolproof to a sufficiently talented fool"
__
OpenStack Development Mailing List (not for usage q
On 18/11/16 15:27, Darragh Bailey - mailing lists wrote:
>
> At this point, now you'll see X, X' & X'', and Y, Y' & Y''. Obviously
> this cause a bit of confusion when listing the changes using:
>
> git log --oneline --graph E~1..local/mitaka
>
> you see some
approaches for different
benefits/trade-offs.
YMMV, and I'm almost certain I'm forgetting some reasons as well ;-)
--
Regards,
Darragh Bailey
IRC: electrofelix
"Nothing is foolproof to a sufficiently talented fool" - Unknown
_
't be
merged in this way, they would get included the same way any other
commit that is merged to the tree currently does, just that there will
be more of them listed.
--
Regards,
Darragh Bailey
IRC: electrofelix
"Nothing is foolproof to a sufficiently talented fool" - Unknown
signat
lock out to a
separate method would make it easier to complete the 'carrying' command
by allowing you to simply call it to do the heavy work of identifying
the previous import merge commit.
> Thanks in advance for anything that might help cut through some of the
> confusion.
>
> Cheer
-requirements.txt
index 63c4a34..3f35ec1 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -9,5 +9,4 @@ python-subunit
testrepository>=0.0.17
testscenarios>=0.4
testtools>=0.9.32
-sphinxcontrib-programoutput
PyYAML>=3.1.0
--
Regards,
Darragh Bailey
IRC: electrofelix
"Not
=0.9,<=0.10.0
+hacking>=0.11.0,<0.12 # Apache-2.0
loremipsum
mock!=1.1.1,<=1.3.0
Sphinx>=1.1.2,<1.2
discover
+coverage>=3.6 # Apache-2.0
fixtures>=0.3.14
python-subunit
testrepository>=0.0.17
--
Regards,
Darragh Bailey
IRC: electrofelix
"Nothing is foolproof
