All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kmo@daterainc.com>
To: David Mohr <damailings@mcbf.net>
Cc: Rolf Fokkens <rolf@rolffokkens.nl>,
	linux-bcache@vger.kernel.org, robie.basak@ubuntu.com,
	g2p.code@gmail.com
Subject: Re: Git repositories
Date: Tue, 27 Jan 2015 14:01:46 -0800	[thread overview]
Message-ID: <20150127220146.GA21432@daterainc.com> (raw)
In-Reply-To: <95adb838f3b8fa76775857cb4268a105@de.mcbf.net>

On Tue, Jan 27, 2015 at 12:00:31AM -0700, David Mohr wrote:
> On 2015-01-26 16:37, Kent Overstreet wrote:
> >Ok, I just merged from him and pushed.
> 
> Great, thanks for getting that worked out so quickly!
> 
> The merge doesn't import the tags though. I think it make sense to set those
> in the evilpiepierate's repository as well:

Ok, tags are pushed too now.

> >On Mon, Jan 26, 2015 at 3:26 PM, Rolf Fokkens <rolf@rolffokkens.nl> wrote:
> >>Well, to be honest I built the latest Fedora bcache-tools packages based
> >>on
> >>https://github.com/g2p/bcache-tools. So I'm perfectly happy with what's
> >>in
> >>it. If all of g2p's repo is merged into
> >>http://evilpiepirate.org/git/bcache-tools.git/ I'll use that one as my
> >>source repo again.
> 
> Thanks for the quick feedback. FWIW, the debian packaging was also built
> upon g2p's repository. But now that there's the active bcache-dev branch on
> the evilpiepirate repository, and the website always refered to that
> repository as well, it was confusing. It seems better to coordinate in one
> central place. We will from now on use evilpiepirate's repository as
> upstream for the Debian packages.

I'm still probably going to be fairly absent for the next couple months
unfortunately - if you guys are happy with what Gabriel is doing I'm fine with
him continuing to maintain bcache tools.

I can give him or someone access to push to my bcache-tools repository so you
guys aren't blocked if I'm off somewhere ignoring email :)

> >>So far I've been collaborating with Gabriel (g2p) using his Github repo
> >>as
> >>the starting point, assuming that's the one that will be pushed to
> >>evilpieprate in the end. At the moment though there are 3 pull requests
> >>pending (one of me) that don't get g2p's attention, I guess he's busy
> >>with
> >>other things. So I'll post my latest pull request here on the mailing
> >>list,
> >>so it can be discussed and Kent can decide if he wants to merge it.
> 
> I'm assuming Gabriel is on the ML? I'd say he should have a chance to merge
> the remaining pull requests - if he doesn't, or says that he doesn't want
> to, then I will post them here on the ML manually for consideration. The
> Debian packages don't currently use any patches.

I would like to see the pull requests (and patches too, ideally) posted on the
mailing list too - just with git send-email. Pull requests are fine, it's just
nice see the patch on the list too.

      reply	other threads:[~2015-01-27 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 21:24 Git repositories David Mohr
2015-01-26 21:45 ` Kent Overstreet
2015-01-26 23:26   ` Rolf Fokkens
2015-01-26 23:37     ` Kent Overstreet
2015-01-27  7:00       ` David Mohr
2015-01-27 22:01         ` Kent Overstreet [this message]

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=20150127220146.GA21432@daterainc.com \
    --to=kmo@daterainc.com \
    --cc=damailings@mcbf.net \
    --cc=g2p.code@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=robie.basak@ubuntu.com \
    --cc=rolf@rolffokkens.nl \
    /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.