From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Source tree tidy Date: Tue, 4 Mar 2014 17:24:26 +0000 Message-ID: <53160C4A.9000105@citrix.com> References: <5310E152.8030407@citrix.com> <21268.27836.723674.210458@mariner.uk.xensource.com> <53146E1D.7060505@citrix.com> <1393914478.10902.22.camel@hastur.hellion.org.uk> <5315C512.3030408@citrix.com> <1393949929.10902.39.camel@hastur.hellion.org.uk> <20140304164541.GE1698@perard.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140304164541.GE1698@perard.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Anthony PERARD Cc: Keir Fraser , Ian Campbell , Ian Jackson , Tim Deegan , Xen-devel List , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 04/03/14 16:45, Anthony PERARD wrote: > On Tue, Mar 04, 2014 at 04:18:49PM +0000, Ian Campbell wrote: >> On Tue, 2014-03-04 at 12:20 +0000, Andrew Cooper wrote: >>> On 04/03/14 06:27, Ian Campbell wrote: >>>>> The signed tags cover 4.1.0-rc1 thru 4.2.0-rc4, missing the releases >>>>> themselves, so are not particularly interesting to verify. >>>> Since the release (and therefore sigs) would have been made on the >>>> X.Y-testing.hg tree perhaps the release tags will be in the release >>>> branch version of the file? Although maybe the original hg->git >>>> conversion didn't pick that up? >>> They have indeed, and the 4.1 and 4.2 trees have further signatures in >>> them. 4.3, 4.4 and unstable hg trees all have the same set of sigs, >>> which do not include the releases. >> Perhaps this is an artefact of the git->hg translation used on 4.3 >> onwards, i..e it only picks up the sigs which are visible from the >> master branch. Perhaps Anthony knows, although I'm not sure how much >> effort it is worth expending here... > That's correct, if the tags was not in master, it won't be visible, like > any other files. > > Also, I tryied to look at exporting tags from git to hg, it was a bit to > complicated, because it required a commit in hg that does not exist in > git. > Yes - the lack of tags in the hg mirrors is an annoyance, but I can see why it is a pain to manage. We (XenServer) do manage without them on the testing.hg trees. ~Andrew