Message130432
I'm not sure if it's intended to be a supported workflow, but I personally have come to like using "mq" for projects where I am an outsider submitting small changes as patches. However, this appears to be a broken workflow due to way getbuildinfo module choose to limit the buildinfo string to 50 characters:
$ hg qnew dummy-patch
$ echo "/* dummy change */" >> Modules/getbuildinfo.c
$ ./python -c 'import sys; print(sys.version)'
3.3a0 (dummy-patch qbase qtip tip:191f047a07b4+, Mar 9 )
[GCC 4.4.5]
This breaks the platform module and therefore breaks the regrtest code, which makes it a show-stopper for using mq to manage your workflow. Is there any reason that length of buildinfo can't be chosen at compile-time based on the sizeof(HGTAG)? |
|
Date |
User |
Action |
Args |
2011-03-09 08:10:17 | scott.dial | set | recipients:
+ scott.dial |
2011-03-09 08:10:17 | scott.dial | set | messageid: <1299658217.91.0.742598203261.issue11450@psf.upfronthosting.co.za> |
2011-03-09 08:10:17 | scott.dial | link | issue11450 messages |
2011-03-09 08:10:17 | scott.dial | create | |
|