Return-Path: 
 <user-return-231-apmail-bloodhound-user-archive=bloodhound.apache.org@bloodhound.apache.org>
X-Original-To: apmail-bloodhound-user-archive@www.apache.org
Delivered-To: apmail-bloodhound-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4F5FC10E86
	for <apmail-bloodhound-user-archive@www.apache.org>;
 Fri,  7 Feb 2014 10:32:56 +0000 (UTC)
Received: (qmail 19297 invoked by uid 500); 7 Feb 2014 10:32:56 -0000
Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org
Received: (qmail 19216 invoked by uid 500); 7 Feb 2014 10:32:52 -0000
Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@bloodhound.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@bloodhound.apache.org>
List-Post: <mailto:user@bloodhound.apache.org>
List-Id: <user.bloodhound.apache.org>
Reply-To: user@bloodhound.apache.org
Delivered-To: mailing list user@bloodhound.apache.org
Received: (qmail 19208 invoked by uid 99); 7 Feb 2014 10:32:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Feb 2014 10:32:51 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of as.kazys@gmail.com designates
 209.85.212.65 as permitted sender)
Received: from [209.85.212.65] (HELO mail-vb0-f65.google.com) (209.85.212.65)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Feb 2014 10:32:44 +0000
Received: by mail-vb0-f65.google.com with SMTP id w18so591397vbj.0
        for <user@bloodhound.apache.org>;
 Fri, 07 Feb 2014 02:32:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=utt7yTwU1YECJa7mogSwiltTqGMtiWBrOnEPrVRGyCQ=;
        b=GYOXqKkoq42UahH0GfQ8luWb71LrOjZva8q/Ri3kjo1Lt16vKC+ytUmmZwYxxENWM/
         nuE0J9hBzQ6skY8HcAfMdzLBgbg4WW4S0gFjaHDHBA2WzyjHXXvpnd7o2LfSBIzS2LV5
         QS65lfCAlb7UwVUyZtywh/odmRcFWV5sE9DJgudVt1Wu6D2hS+jiTEi8i8kJwAGS4AmY
         Fgz/Xf9IuhOR5UYljEadk5H6ymNztk442flGM6NVav1zw6RwQ6b6v4kMqz2/7JLOtU7l
         mQ7xTxqjQsN+uOewqFKT2mKlZhJTf3vv66rd0l0+BZTp6Yor+9Y7s1hk8uxAroV6eyen
         RSOw==
MIME-Version: 1.0
X-Received: by 10.58.58.3 with SMTP id m3mr114369veq.32.1391769143775; Fri, 07
 Feb 2014 02:32:23 -0800 (PST)
Received: by 10.220.127.72 with HTTP; Fri, 7 Feb 2014 02:32:23 -0800 (PST)
Date: Fri, 7 Feb 2014 12:32:23 +0200
Message-ID: 
 <CAMtfQunLP6gVQ=NYVEN=URyxoMBzidzydbaJiHC+K7RvgtaHuQ@mail.gmail.com>
Subject: Migrating multiple tracs as separate projects in bloodhound.
From: Kazys <as.kazys@gmail.com>
To: user@bloodhound.apache.org
Content-Type: text/plain; charset=UTF-8
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

how could I migrate multiple tracs as separate projects in one
bloodhound installation?

--
Kazys