From: Casey Dahlin <cdahlin@redhat.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Introduce git-hive
Date: Sun, 5 Sep 2010 22:25:33 -0400 [thread overview]
Message-ID: <20100906022532.GA15150@foucault.redhat.com> (raw)
In-Reply-To: <20100905194810.5940F384096@mbox.dmi.unict.it>
On Sun, Sep 05, 2010 at 09:48:06PM +0200, Giuseppe Bilotta wrote:
> Casey Dahlin wrote:
> >
> > So now our two peers can see each other.
> >
> > casey@host_a$ git hive show --branches
> > Nguyen Thai Ngoc Duy <pclouds@gmail.com>
> > master
> > for_casey
> >
> > ---
> >
> > nguyen@host_b$ git hive show --branches
> > Casey Dahlin <cdahlin@redhat.com>
> > master
> > stable
> > v2.1
> >
> > And we can exchange them
> >
> > casey@host_a$ git hive fetch nguyen for_casey
> > casey@host_a$ git branch
> > * master
> > stable
> > for_casey
> >
> > Note that the two arguments in fetch are a regex which searches through
> > user IDs and a branch name, which is why I can abbreviate to just "nguyen"
> > in all lower case.
>
> I may be a little late into the discussion, but I must say I very much like the
> idea. I realize that this is mostly intended for local repo sharing (typically
> between coworkers), but I suspect the idea could be extended to more general
> distributed repository, ehrm, distribution.
>
> The only thing I would object to, so far, is hive fetch bringing stuff
> directly into my local repository. I typically prefer content to remain
> fenced in its appropriate namespace (e.g. I have issues even with the way tags
> and notes are imported from remotes). For hives, it might be a better idea to
> have the hive-fetched branches plop into either refs/remotes or maybe even a
> new dedicated namespace like refs/hive/ ?
Plan is to kill hive-fetch in favor of a fetch helper so the ordinary git
retrieval commands may be used.
--CJD
prev parent reply other threads:[~2010-09-06 2:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 19:59 [RFC PATCH] Introduce git-hive cdahlin
2010-08-30 21:17 ` Luke Kenneth Casson Leighton
2010-08-31 1:29 ` Nguyen Thai Ngoc Duy
2010-08-31 14:38 ` Casey Dahlin
2010-08-31 15:08 ` Luke Kenneth Casson Leighton
2010-08-31 15:52 ` Casey Dahlin
2010-08-31 16:47 ` Luke Kenneth Casson Leighton
2010-08-31 17:20 ` Casey Dahlin
[not found] ` <815C806E-E7DC-4B7D-9B45-4C9B289DFEEF@sb.org>
2010-08-31 19:19 ` Casey Dahlin
2010-08-31 19:21 ` Kevin Ballard
2010-08-31 19:25 ` Casey Dahlin
2010-09-05 20:08 ` Tomas Carnecky
2010-09-06 2:28 ` Casey Dahlin
2010-08-31 19:23 ` Kevin Ballard
2010-09-01 3:56 ` Ilari Liusvaara
2010-09-01 4:07 ` Casey Dahlin
2010-09-05 19:48 ` Giuseppe Bilotta
[not found] ` <20100905194810.5940F384096@mbox.dmi.unict.it>
2010-09-06 2:25 ` Casey Dahlin [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=20100906022532.GA15150@foucault.redhat.com \
--to=cdahlin@redhat.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=pclouds@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.
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 NNTP newsgroup(s).