From: Johan Herland <johan@herland.net>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git discussion list <git@vger.kernel.org>,
Jeff King <peff@peff.net>, Vicent Marti <tanoku@gmail.com>,
Brad King <brad.king@kitware.com>
Subject: Re: [RFC/WIP] Pluggable reference backends
Date: Mon, 10 Mar 2014 12:44:23 +0100 [thread overview]
Message-ID: <CALKQrgfczpUU6Lh+hf867UOYUge2qsBTBTknwAk2pvRF6=xi4A@mail.gmail.com> (raw)
In-Reply-To: <531D9B50.5030404@alum.mit.edu>
On Mon, Mar 10, 2014 at 12:00 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
> I have started working on pluggable ref backends. In this email I
> would like to share my plans and solicit feedback.
No comments or useful feedback yet, except that I enthusiastically
approve of the objective and the plan you have for how to get there.
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2014-03-10 11:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 11:00 [RFC/WIP] Pluggable reference backends Michael Haggerty
2014-03-10 11:44 ` Johan Herland [this message]
2014-03-10 14:30 ` Shawn Pearce
2014-03-10 15:51 ` Max Horn
2014-03-10 15:52 ` Jeff King
2014-03-10 16:14 ` David Kastrup
2014-03-10 16:28 ` David Lang
2014-03-10 19:42 ` Jeff King
2014-03-10 19:56 ` David Kastrup
2014-03-10 17:46 ` Junio C Hamano
2014-03-10 17:56 ` Jeff King
2014-03-10 21:07 ` Michael Haggerty
2014-03-11 2:39 ` Shawn Pearce
2014-03-12 10:26 ` egit vs. git behaviour (was: [RFC/WIP] Pluggable reference backends) Andreas Krey
2014-03-12 16:48 ` Shawn Pearce
2014-03-11 10:56 ` [RFC/WIP] Pluggable reference backends Karsten Blees
2014-03-12 11:43 ` Michael Haggerty
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALKQrgfczpUU6Lh+hf867UOYUge2qsBTBTknwAk2pvRF6=xi4A@mail.gmail.com' \
--to=johan@herland.net \
--cc=brad.king@kitware.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=tanoku@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).