From: Robie Basak <robie.basak@ubuntu.com>
To: linux-bcache@vger.kernel.org
Subject: Re: bcache-tools ITP
Date: Wed, 17 Sep 2014 14:08:05 +0100 [thread overview]
Message-ID: <20140917130805.GX29881@mal.justgohome.co.uk> (raw)
In-Reply-To: <20140917115538.GW29881@mal.justgohome.co.uk>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Wed, Sep 17, 2014 at 12:55:38PM +0100, Robie Basak wrote:
> Can we define which the canonical upstream source tree is, please, and
> where the canonical Debian packaging branch should be? Then we can work
> on pushing the changes back to the right places, rather than having
> scattered branches all over the place. I noticed some changes to the
> upstream source that don't appear to be in branch 1, for example.
I've looked again and I see that 1.0.7 is tagged in the Github repos,
but not in evilpiepirate.org/git/bcache-tools.git.
Does this mean that the Github repos are now the canonical upstream?
Should the page at http://bcache.evilpiepirate.org/ be changed?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-17 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140530155757.GU2893@mal.justgohome.co.uk>
[not found] ` <175f4ae1c88f5506984eb3a1673829a5@de.mcbf.net>
[not found] ` <20140715111552.GA17765@mal.justgohome.co.uk>
2014-09-17 11:55 ` bcache-tools ITP Robie Basak
2014-09-17 13:08 ` Robie Basak [this message]
2014-09-17 22:35 ` David Mohr
2014-09-18 17:26 ` Rolf Fokkens
2014-09-17 23:21 ` Darrick J. Wong
2014-09-18 7:59 ` Robie Basak
2014-09-18 18:19 ` Darrick J. Wong
2014-09-18 17:18 ` Rolf Fokkens
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=20140917130805.GX29881@mal.justgohome.co.uk \
--to=robie.basak@ubuntu.com \
--cc=linux-bcache@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox