From: David Aguilar <davvid@gmail.com>
To: Hans-Christoph Steiner <hans@at.or.at>
Cc: git@vger.kernel.org
Subject: Re: developing a modified Linux-style workflow
Date: Sun, 12 Dec 2010 19:31:47 -0800 [thread overview]
Message-ID: <20101213033145.GA3609@gmail.com> (raw)
In-Reply-To: <7EAE16CF-A9A8-47A6-9294-3646CCDB0E9C@at.or.at>
On Sun, Dec 12, 2010 at 05:24:16PM -0500, Hans-Christoph Steiner wrote:
>
> Hey all,
>
> (and my second post on this list...)
>
> I've gotten pretty good at git, and its helping me already with
> managing the very odd workflows I have with the software I work a
> lot on called Pd (http://puredata.info). My role in Pd development
> is like a Linux lieutenant.
>
> I also the main dev for an app called Pd-extended, which is based on
> Pd. Now I'm stuck trying to figure out how to use git to match my
> current workflow for Pd-extended, which is a kind of long-lived
> branch, almost like a friendly fork. So its kind of close to the
> Linux workflow with me as a lieutenant, but not quite.
>
> What makes it tricky is that I make releases directly from my repo
> that are widely used. So my repo is both lieutenant and dictator at
> the same time. So that's where I am stumped. I want to be able to
> rebase and push to a public repo, but that would be stupid. So
> there has got to be another way.
Have you considered periodically merging Pd into Pd-extended
as an alternative to rebasing? It might even be easier to
manage in the long-term.
--
David
next prev parent reply other threads:[~2010-12-13 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 22:24 developing a modified Linux-style workflow Hans-Christoph Steiner
2010-12-13 3:31 ` David Aguilar [this message]
2010-12-13 3:23 ` Hans-Christoph Steiner
2010-12-13 16:15 ` Neal Kreitzinger
[not found] <E54235A96EB484418EBD9509F37176D210049C61@htmail10.hightouchinc.com>
2011-01-04 19:01 ` Hans-Christoph Steiner
2011-01-04 21:19 ` Neal Kreitzinger
2011-01-05 0:47 ` Neal Kreitzinger
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=20101213033145.GA3609@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=hans@at.or.at \
/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).