From: Jameson Rollins <jrollins@finestructure.net>
To: micah anderson <micah@riseup.net>,
sebastian@sspaeth.de, notmuch@notmuchmail.org
Subject: Re: Git feature branch
Date: Wed, 27 Jan 2010 14:19:54 -0500 [thread overview]
Message-ID: <87aavz1hk5.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87wrz4fqsw.fsf@lillypad.riseup.net>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
On Wed, 27 Jan 2010 11:24:15 +1300, micah anderson <micah@riseup.net> wrote:
> Couldn't all of this be done without moving the existing git repository
> (don't forget that transition is a cost)? Those who wish to put together
> these proposed branches go ahead and do so, publishing those wherever
> they like (git.debian.org, gitorious, their own hosted git repositories,
> or even github) and then Carl can just add those as remotes as he sees
> fit.
I second this idea. I've been working on quite a few projects that work
in this way, with nothing but personal distributed repos, and it works
quite well. Especially if Carl is going to continue to be benevolent
dictator (as I agree that he should). Everyone who has patches can just
post them to their personal repos, making sure that they're well rebased
to Carl's master, and Carl can just pull from them as he sees fit. It's
what git is designed to do, and it actually works really well.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2010-01-27 19:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 14:00 Git feature branch Sebastian Spaeth
2010-01-20 20:00 ` micah anderson
2010-01-22 8:09 ` Sebastian Spaeth
2010-01-22 8:50 ` Sebastian Spaeth
2010-01-22 21:10 ` Carl Worth
2010-01-25 21:32 ` martin f krafft
2010-01-26 0:46 ` sebastian
2010-01-26 22:24 ` micah anderson
2010-01-27 19:17 ` Ben Gamari
2010-02-24 18:58 ` Carl Worth
2010-01-27 19:19 ` Jameson Rollins [this message]
2010-01-27 19:41 ` martin f krafft
2010-01-28 7:05 ` James Rowe
2010-02-01 22:31 ` patchwork test instance (was: Git feature branch) martin f krafft
2010-02-02 11:38 ` Marten Veldthuis
2010-02-10 3:25 ` patchwork test instance martin f krafft
2010-02-10 8:49 ` David Bremner
2010-02-10 22:00 ` martin f krafft
2010-02-10 9:25 ` Sebastian Spaeth
2010-02-10 22:22 ` martin f krafft
2010-02-24 19:10 ` Carl Worth
2010-02-24 20:39 ` martin f krafft
2010-02-24 19:08 ` Carl Worth
2010-02-25 8:06 ` martin f krafft
2010-02-04 3:05 ` Git feature branch Carl Worth
2010-02-04 3:50 ` martin f krafft
2010-02-05 3:36 ` patchwork now auto-updates patches from Git (was: Git feature branch) martin f krafft
2010-02-04 3:58 ` Git feature branch Jameson Rollins
2010-02-24 19:13 ` Carl Worth
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aavz1hk5.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=micah@riseup.net \
--cc=notmuch@notmuchmail.org \
--cc=sebastian@sspaeth.de \
/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://yhetil.org/notmuch.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).