[Bug 4230] New: Heads information may flood the user during push.

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Wed Apr 23 22:17:55 CDT 2014


http://bz.selenic.com/show_bug.cgi?id=4230

          Priority: normal
            Bug ID: 4230
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Heads information may flood the user during push.
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: pierre-yves.david at ens-lyon.org
          Hardware: PC
            Status: UNCONFIRMED
           Version: 3.0-rc
         Component: Mercurial
           Product: Mercurial

Having a "sink" repo where people push lots of heads but never pull is a fairly
common setup. A simple example is the Mozilla's "try" server where people push
to get complete test run executed.

However, in 3.0rc, the list of remotly unknown heads is deplayed on push. This
give ridiculously cluttered output as show below:

  pushing to ssh://marmoute@firefly.edlund.dk/mercurial-testing/
  searching for changes
  remote has heads on branch 'default' that are not known locally: 00594bfe2759
01daa33a1bd9 033ab1bd7518 0b2e16a1f6f5 0ca57a87852f 0fa78f86a99e 120f0b3b91d1
16dcf36d4e8a 19602359f817 19b576c34f05 1c57366420e4 20a593e1e6d5 21aa68e8bad3
21d2db8ecec3 2440ec3579aa 24901c1dcfd3 26ae9ce11f50 29d8b1412844 2a108296c69a
2d87e5d6ebbc 2e965326695f 2f9dbb2d7781 3425f4e04486 370400a33a50 378a00b2ea89
3e5901d9639f 41a5810bb9cb 4310a1bb5ccd 44c84a033e5a 461e34c28f80 4d3ae8c11254
4fe17876f3bc 508c361a0b90 52cccd5a1842 536a696b0162 5db7f0c6eddd 5e90212f89e0
5f4c0dc22275 5fd76fc61092 65e5e96719c5 6a8c43e60a89 6cb2333190c6 6e0c775e67c1
7168b601a7f6 73098488dcad 7bf15755030c 7d388a8fa1b3 80dcf4b68053 8ca9e0ce5328
8de68237ff68 9111e44e676f 91a5cc6d8b45 91fdf5b92fda 9339086330a5 953eeff09e84
96d2d9943df8 9ba08ae3b887 a1c73ee5ab30 a337eefafeb2 a5e84385dfcb ad74dfd8bd3a
b03628c8077c b0ad5a3d7f9e b1e5c5372161 bbb657264e9f bc751da458ab bc915aaaa197
c0255e5ef1b8 c66557660b15 c73d82f5c006 c7de0b708032 cb89a2941f31 d4aa91446343
d82b9b09a339 da808d76ea52 da95185e9c6d dc3225293fbe dcaaa00ee876 dd6c8d7a3266
dd8179a418cd e36eaa4a6549 e710bcfc8c80 e8e20050a56d eb85d90e5611 ed7e9bcf8b40
ee41df514fbf f086e571d4ae f190f2c56e58 f3e6e619ef38 f662793c0141 f6b5ec1b842a
f6f203c97b67 f7725ce07f21 f95cde4e9928 f98fc450d8dc fb5b0ebef11e fe90c312113f
ffcc9dbcd240
  remote has heads on branch 'stable' that are not known locally: 0baafe6ee2c0
162b1c2261ca 23f4171aa191 2fac509b1b16 4be1d06df73f 616b4bbf7e2a 6253c91f1506
64570ea6f7d0 6c667e5abbc5 8d67c8017cee 8da7875b5181 8e68bee823e2 94fa59f68e5a
bbfd99638de5 cabb74a6dc7a e4bb526c0182 e5d7a2e073d7
  remote: adding changesets
  remote: adding manifests
  remote: adding file changes
  remote: added 29 changesets with 43 changes to 27 files (+11 heads)
  remote: 22 files updated, 0 files merged, 0 files removed, 0 files unresolved

I recommend falling back to a simpler message when there is more than a couple
extra heads

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list