{"thread":{"id":"9073","subject":"git bisect not accepting -git kernels","startedAt":"2007-07-17T16:03:02Z","lastAt":"2007-07-17T17:15:38Z","messageCount":11,"participants":["Amit Walambe","Peter Baumann","Thomas Glanzmann","Sam Ravnborg","René Scharfe","Julian Phillips","Rogan Dawes"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"47637","messageId":"469CE836.6010508@arcom.com","threadId":"9073","inReplyTo":null,"subject":"git bisect not accepting -git kernels","fromName":"Amit Walambe","fromEmail":"awalambe@arcom.com","sentAt":"2007-07-17T16:03:02Z","receivedAt":"2007-07-17T16:03:02Z","isPatch":false,"sender":{"key":"awalambe@arcom.com","avatar":null},"body":"Hi!\nI was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For \nwhich I get following error :\nroot@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\nBad rev input: v2.6.22-git6\n\nThe repository is obtained by :\nroot@amit:/usr/src # git clone \ngit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git\n\nI am running following git version on Debian Sid, updated today.\n# git --version\ngit version 0.99.8.GIT\n'# dpkg -l | grep git' shows ' git-core \n1:1.5.2.3-1'\n\nI tried searching man-pages/documentation/website but couldn't find any \nreferences to git bisect on -git kernels. I would be grateful if anyone \ncan help me find what's going wrong.\n\nAs I am not subscribed to the mailing-list, please cc me to all the \nmessages on the thread.\nThanks and Regards,\n-- \nAmit Walambe\nDesign Engineer, Arcom Control Systems Ltd.\nhttp://www.arcom.com\nTel: +44-(0)1223 411200 ext. 3204\nDirect: +44-(0)1223 403465\n\n_____________________________________________________________________\nThe message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.\n\nThis message has been virus scanned by MessageLabs.\n"},{"id":"47640","messageId":"20070717161344.GB4815@xp.machine.xx","threadId":"9073","inReplyTo":"469CE836.6010508@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"Peter Baumann","fromEmail":"waste.manager@gmx.de","sentAt":"2007-07-17T16:13:44Z","receivedAt":"2007-07-17T16:13:44Z","isPatch":false,"sender":{"key":"waste.manager@gmx.de","avatar":null},"body":"On Tue, Jul 17, 2007 at 05:03:02PM +0100, Amit Walambe wrote:\n> Hi!\n> I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For which I \n> get following error :\n> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n> Bad rev input: v2.6.22-git6\n>\n> The repository is obtained by :\n> root@amit:/usr/src # git clone \n> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git\n>\n> I am running following git version on Debian Sid, updated today.\n> # git --version\n> git version 0.99.8.GIT\n\nThere is a very old GIT version in your PATH (version 0.99*), which\ntakes preference over the version from sid.\n\n> '# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'\n>\n\n-Peter\n"},{"id":"47642","messageId":"20070717161607.GD16209@cip.informatik.uni-erlangen.de","threadId":"9073","inReplyTo":"469CE836.6010508@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"Thomas Glanzmann","fromEmail":"thomas@glanzmann.de","sentAt":"2007-07-17T16:16:07Z","receivedAt":"2007-07-17T16:16:07Z","isPatch":false,"sender":{"key":"thomas@glanzmann.de","avatar":null},"body":"Hello,\n\n> # git --version\n> git version 0.99.8.GIT\n\nthis doesn't match\n\n> '# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'\n\nthat. Maybe you should build your own git packages. Lucky you that it is\npretty easy with debian. Have a look at this thread:\n\n\thttp://groups.google.com/group/linux.kernel/browse_thread/thread/b8509269407c0fdc/d05d0547e7dfcf03?lnk=st&q=author%3AThomas+author%3AGlanzmann+git+linux.kernel&rnum=1#d05d0547e7dfcf03\n\nespecially the first post (scroll up).\n\n\tThomas\n"},{"id":"47645","messageId":"469CF00C.4040906@arcom.com","threadId":"9073","inReplyTo":"20070717161607.GD16209@cip.informatik.uni-erlangen.de","subject":"Re: git bisect not accepting -git kernels","fromName":"Amit Walambe","fromEmail":"awalambe@arcom.com","sentAt":"2007-07-17T16:36:28Z","receivedAt":"2007-07-17T16:36:28Z","isPatch":false,"sender":{"key":"awalambe@arcom.com","avatar":null},"body":"Hi,\nThanks for both the replies.\n\nThomas Glanzmann wrote:\n> Hello,\n> \n>> # git --version\n>> git version 0.99.8.GIT\n> \n> this doesn't match\n> \n>> '# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'\nThis struck me as being weird, but I thought 'git' utility version is \ndifferent than the package. My mistake! :)\n\n> that. Maybe you should build your own git packages. Lucky you that it is\n> pretty easy with debian. Have a look at this thread:\nI didn't build my own git version. What I did do was to remove the old \ngit and ensure I am using the Debian installed one.\n\nNow I am getting a different error :\nroot@amit:/usr/src/linux-git # which git\n/usr/bin/git\nroot@amit:/usr/src/linux-git # git --version\ngit version 1.5.2.3\nroot@amit:/usr/src/linux-git # git bisect good v2.6.22-rc6\nroot@amit:/usr/src/linux-git # git bisect bad v2.6.22-rc8\nfatal: Needed a single revision\nroot@amit:/usr/src/linux-git #\n\nA quick search on the net didn't yield anything. Please help me find out \nwhat's going wrong.\nThanks and Regards,\n-- \nAmit Walambe\nDesign Engineer, Arcom Control Systems Ltd.\nhttp://www.arcom.com\nTel: +44-(0)1223 411200 ext. 3204\nDirect: +44-(0)1223 403465\n\n_____________________________________________________________________\nThe message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.\n\nThis message has been virus scanned by MessageLabs.\n"},{"id":"47646","messageId":"20070717164436.GA26953@uranus.ravnborg.org","threadId":"9073","inReplyTo":"469CE836.6010508@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"Sam Ravnborg","fromEmail":"sam@ravnborg.org","sentAt":"2007-07-17T16:44:36Z","receivedAt":"2007-07-17T16:44:36Z","isPatch":false,"sender":{"key":"sam@ravnborg.org","avatar":"https://gravatar.com/avatar/168a912606ed0742d840bb365e3cc21db390c36531a58341dc7a069cc1f15f62?d=mp&s=160"},"body":"On Tue, Jul 17, 2007 at 05:03:02PM +0100, Amit Walambe wrote:\n> Hi!\n> I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For \n> which I get following error :\n> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n> Bad rev input: v2.6.22-git6\n> \n> The repository is obtained by :\n> root@amit:/usr/src # git clone \n> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git\n\nThe -git# is added by a script and does not exists as tags.\nThe same place where you retreive the -git files has a file identifying\nthe commit that is the latest - use the SHA of this and you should\nbe happy.\n\n\tSam\n"},{"id":"47647","messageId":"469CF2E6.1020104@lsrfire.ath.cx","threadId":"9073","inReplyTo":"469CE836.6010508@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"René Scharfe","fromEmail":"rene.scharfe@lsrfire.ath.cx","sentAt":"2007-07-17T16:48:38Z","receivedAt":"2007-07-17T16:48:38Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Amit Walambe schrieb:\n> Hi!\n> I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For\n> which I get following error :\n> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n> Bad rev input: v2.6.22-git6\n> \n> The repository is obtained by :\n> root@amit:/usr/src # git clone\n> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git\n> \n> I am running following git version on Debian Sid, updated today.\n> # git --version\n> git version 0.99.8.GIT\n> '# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'\n> \n> I tried searching man-pages/documentation/website but couldn't find any\n> references to git bisect on -git kernels. I would be grateful if anyone\n> can help me find what's going wrong.\n\nThe -git snapshots are made automatically by kernel.org, and their name\nis not included in the git repository.  You could create tags for them\nlike this:\n\n git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809\n git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa\n\n... and afterwards you can use those revision names with bisect (or\nother git commands).  I've got the commit IDs (i.e. those mysterious 40\nhex digits above) from the first line of the changelogs; their URLs are:\n\n http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log\n http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log\n\nRené\n"},{"id":"47648","messageId":"469CF52D.10407@arcom.com","threadId":"9073","inReplyTo":"469CF2E6.1020104@lsrfire.ath.cx","subject":"Re: git bisect not accepting -git kernels","fromName":"Amit Walambe","fromEmail":"awalambe@arcom.com","sentAt":"2007-07-17T16:58:21Z","receivedAt":"2007-07-17T16:58:21Z","isPatch":false,"sender":{"key":"awalambe@arcom.com","avatar":null},"body":"Thanks a ton everyone for all the replies.\nHere is the current status :\n\nRené Scharfe wrote:\n> Amit Walambe schrieb:\n>> Hi!\n>> I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For\n>> which I get following error :\n>> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n>> Bad rev input: v2.6.22-git6\n> \n> The -git snapshots are made automatically by kernel.org, and their name\n> is not included in the git repository.  You could create tags for them\n> like this:\n> \n>  git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809\n>  git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa\n> \n> ... and afterwards you can use those revision names with bisect (or\n> other git commands).  I've got the commit IDs (i.e. those mysterious 40\n> hex digits above) from the first line of the changelogs; their URLs are:\n> \n>  http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log\n>  http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log\nI found the commit ids in following file as well :\nhttp://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.id\nhttp://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.id\n\nBut telling good/bad points to git bisect still fails, whether I pass \nthe commit-id or the tags I created with commands given by René :\n\nroot@amit:/usr/src/linux-git # git bisect good \n8f41958bdd577731f7411c9605cfaa9db6766809\ncat: .git/BISECT_NAMES: No such file or directory\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git # git tag v2.6.22-git6 \n8f41958bdd577731f7411c9605cfaa9db6766809\nroot@amit:/usr/src/linux-git # git tag v2.6.22-git8 \na5fcaa210626a79465321e344c91a6a7dc3881fa\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\ncat: .git/BISECT_NAMES: No such file or directory\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8\ncat: .git/BISECT_NAMES: No such file or directory\n\nThanks and Regards,\n-- \nAmit Walambe\nDesign Engineer, Arcom Control Systems Ltd.\nhttp://www.arcom.com\nTel: +44-(0)1223 411200 ext. 3204\nDirect: +44-(0)1223 403465\n\n_____________________________________________________________________\nThe message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.\n\nThis message has been virus scanned by MessageLabs.\n"},{"id":"47649","messageId":"469CF70B.7080207@arcom.com","threadId":"9073","inReplyTo":"469CF00C.4040906@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"Amit Walambe","fromEmail":"awalambe@arcom.com","sentAt":"2007-07-17T17:06:19Z","receivedAt":"2007-07-17T17:06:19Z","isPatch":false,"sender":{"key":"awalambe@arcom.com","avatar":null},"body":"Amit Walambe wrote:\n> I didn't build my own git version. What I did do was to remove the old \n> git and ensure I am using the Debian installed one.\n> \n> Now I am getting a different error :\n> root@amit:/usr/src/linux-git # which git\n> /usr/bin/git\n> root@amit:/usr/src/linux-git # git --version\n> git version 1.5.2.3\n> root@amit:/usr/src/linux-git # git bisect good v2.6.22-rc6\n> root@amit:/usr/src/linux-git # git bisect bad v2.6.22-rc8\n> fatal: Needed a single revision\n> root@amit:/usr/src/linux-git #\nI should call it a day. Above commands are wrong. I need to work on -git \nkernels and not -rc kernels (as the above commands are showing).\nI am still getting the same errors I started with :\n\nroot@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\nBad rev input: v2.6.22-git6\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git #\nroot@amit:/usr/src/linux-git # git bisect good v2.6.22-git8\nBad rev input: v2.6.22-git8\n\n> A quick search on the net didn't yield anything. Please help me find out \n> what's going wrong.\n> Thanks and Regards,\nThe above greatly applies :)\n-- \nAmit Walambe\nDesign Engineer, Arcom Control Systems Ltd.\nhttp://www.arcom.com\nTel: +44-(0)1223 411200 ext. 3204\nDirect: +44-(0)1223 403465\n\n_____________________________________________________________________\nThe message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.\n\nThis message has been virus scanned by MessageLabs.\n"},{"id":"47650","messageId":"Pine.LNX.4.64.0707171809190.29062@reaper.quantumfyre.co.uk","threadId":"9073","inReplyTo":"469CF52D.10407@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2007-07-17T17:10:44Z","receivedAt":"2007-07-17T17:10:44Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"On Tue, 17 Jul 2007, Amit Walambe wrote:\n\n> But telling good/bad points to git bisect still fails, whether I pass the \n> commit-id or the tags I created with commands given by René :\n>\n> root@amit:/usr/src/linux-git # git bisect good \n> 8f41958bdd577731f7411c9605cfaa9db6766809\n> cat: .git/BISECT_NAMES: No such file or directory\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git # git tag v2.6.22-git6 \n> 8f41958bdd577731f7411c9605cfaa9db6766809\n> root@amit:/usr/src/linux-git # git tag v2.6.22-git8 \n> a5fcaa210626a79465321e344c91a6a7dc3881fa\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n> cat: .git/BISECT_NAMES: No such file or directory\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8\n> cat: .git/BISECT_NAMES: No such file or directory\n>\n> Thanks and Regards,\n>\n\nyou seem to be missing a \"git bisect start\" from that sequence ... see the \nman page for more details.\n\n-- \nJulian\n\n  ---\nPeter Griffin:  You wanna talk about awkward moments? Once, during sex, I called Lois \"Frank\". Your move, Sherlock."},{"id":"47651","messageId":"469CF830.8040601@dawes.za.net","threadId":"9073","inReplyTo":"469CF52D.10407@arcom.com","subject":"Re: git bisect not accepting -git kernels","fromName":"Rogan Dawes","fromEmail":"discard@dawes.za.net","sentAt":"2007-07-17T17:11:12Z","receivedAt":"2007-07-17T17:11:12Z","isPatch":false,"sender":{"key":"discard@dawes.za.net","avatar":null},"body":"Amit Walambe wrote:\n> Thanks a ton everyone for all the replies.\n> Here is the current status :\n> \n> René Scharfe wrote:\n>> Amit Walambe schrieb:\n>>> Hi!\n>>> I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For\n>>> which I get following error :\n>>> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n>>> Bad rev input: v2.6.22-git6\n>>\n>> The -git snapshots are made automatically by kernel.org, and their name\n>> is not included in the git repository.  You could create tags for them\n>> like this:\n>>\n>>  git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809\n>>  git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa\n>>\n>> ... and afterwards you can use those revision names with bisect (or\n>> other git commands).  I've got the commit IDs (i.e. those mysterious 40\n>> hex digits above) from the first line of the changelogs; their URLs are:\n>>\n>>  http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log\n>>  http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log\n> I found the commit ids in following file as well :\n> http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.id\n> http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.id\n> \n> But telling good/bad points to git bisect still fails, whether I pass \n> the commit-id or the tags I created with commands given by René :\n> \n> root@amit:/usr/src/linux-git # git bisect good \n> 8f41958bdd577731f7411c9605cfaa9db6766809\n> cat: .git/BISECT_NAMES: No such file or directory\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git # git tag v2.6.22-git6 \n> 8f41958bdd577731f7411c9605cfaa9db6766809\n> root@amit:/usr/src/linux-git # git tag v2.6.22-git8 \n> a5fcaa210626a79465321e344c91a6a7dc3881fa\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n> cat: .git/BISECT_NAMES: No such file or directory\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git #\n> root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8\n> cat: .git/BISECT_NAMES: No such file or directory\n> \n> Thanks and Regards,\n\nYou need to start off by saying\n\n$ git bisect start\n\nto set up the necessary infrastructure.\n\nRogan\n"},{"id":"47654","messageId":"469CF93A.9070802@arcom.com","threadId":"9073","inReplyTo":"Pine.LNX.4.64.0707171809190.29062@reaper.quantumfyre.co.uk","subject":"Re: git bisect not accepting -git kernels","fromName":"Amit Walambe","fromEmail":"awalambe@arcom.com","sentAt":"2007-07-17T17:15:38Z","receivedAt":"2007-07-17T17:15:38Z","isPatch":false,"sender":{"key":"awalambe@arcom.com","avatar":null},"body":"Julian Phillips wrote:\n> On Tue, 17 Jul 2007, Amit Walambe wrote:\n> \n>> But telling good/bad points to git bisect still fails, whether I pass \n>> the commit-id or the tags I created with commands given by René :\n>>\n>> root@amit:/usr/src/linux-git # git bisect good \n>> 8f41958bdd577731f7411c9605cfaa9db6766809\n>> cat: .git/BISECT_NAMES: No such file or directory\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git # git tag v2.6.22-git6 \n>> 8f41958bdd577731f7411c9605cfaa9db6766809\n>> root@amit:/usr/src/linux-git # git tag v2.6.22-git8 \n>> a5fcaa210626a79465321e344c91a6a7dc3881fa\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\n>> cat: .git/BISECT_NAMES: No such file or directory\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git #\n>> root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8\n>> cat: .git/BISECT_NAMES: No such file or directory\n>>\n>> Thanks and Regards,\n>>\n> \n> you seem to be missing a \"git bisect start\" from that sequence ... see \n> the man page for more details.\nYes indeed. Somehow the state was messed up due to different commands I \nhad tried. Now it works ok.\nroot@amit:/usr/src/linux-git # git bisect good v2.6.22-git6\nroot@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8\nBisecting: 362 revisions left to test after this\n[02b2318e07f98a7cdf7089a4457a8d62424aa824] Merge branch 'master' of \nmaster.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6\nThanks a lot for everyone for their help. _Much appreciated_!\nBest Regards,\n-- \nAmit Walambe\nDesign Engineer, Arcom Control Systems Ltd.\nhttp://www.arcom.com\nTel: +44-(0)1223 411200 ext. 3204\nDirect: +44-(0)1223 403465\n\n_____________________________________________________________________\nThe message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to and from Arcom is automatically monitored for operational and lawful business reasons.\n\nThis message has been virus scanned by MessageLabs.\n"}]}