All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: Source tree tidy
Date: Mon, 3 Mar 2014 11:57:17 +0000	[thread overview]
Message-ID: <53146E1D.7060505@citrix.com> (raw)
In-Reply-To: <21268.27836.723674.210458@mariner.uk.xensource.com>

On 03/03/14 11:51, Ian Jackson wrote:
> Andrew Cooper writes ("Source tree tidy"):
>> Looking through the root of the git tree, there are some files which
>> appear to be remnants of legacy source code management systems, and thus
>> are good candidates for deletion.
>>
>> >From bitkeeper:
>> .bk-to-hg
>> .rootkeys
>> .hg-to-bk
> I have no idea what these are but if we think anyone is using
> bitkeeper I would want an explanation of what they are and what
> implications there might be for removing them.
>
> But probably no-one is using bitkeeper, in which case we can remove
> them.
>
>> >From mercurial:
>> .hgsigs
> Doesn't this latter contain information which hg needs if it wants to
> verify a signed tag which was made with hg ?
>
> Ian.

In theory, yes, although in practice the public half of the key used to
sign them doesn't appear to be published.

The signed tags cover 4.1.0-rc1 thru 4.2.0-rc4, missing the releases
themselves, so are not particularly interesting to verify.

~Andrew

  reply	other threads:[~2014-03-03 11:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 19:19 Source tree tidy Andrew Cooper
2014-03-03 11:51 ` Ian Jackson
2014-03-03 11:57   ` Andrew Cooper [this message]
2014-03-04  6:27     ` Ian Campbell
2014-03-04  6:49       ` Ian Campbell
2014-03-04 12:13         ` Russell Pavlicek
2014-03-04 16:21           ` Ian Campbell
2014-03-04 16:31             ` Russell Pavlicek
2014-03-04 16:34               ` Ian Jackson
2014-03-04 16:36                 ` Russell Pavlicek
2014-03-04 16:46                 ` Russell Pavlicek
2014-03-04 16:51                   ` Ian Jackson
2014-03-04 16:53                     ` Russell Pavlicek
2014-03-04 17:53                     ` Russell Pavlicek
2014-03-05  1:39                 ` Ian Campbell
2014-03-05  1:40                   ` Russell Pavlicek
2014-03-04 12:16         ` Ian Jackson
2014-03-04 12:35           ` Russell Pavlicek
2014-03-04 16:20           ` Ian Campbell
2014-03-04 12:20       ` Andrew Cooper
2014-03-04 16:18         ` Ian Campbell
2014-03-04 16:45           ` Anthony PERARD
2014-03-04 17:24             ` Andrew Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53146E1D.7060505@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.