X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sat, 16 Jan 2016 14:12:08 -0500
Message-Id: <201601161912.u0GJC8Fs025943@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <569A3280.3030704@iee.org> (geda-user@delorie.com)
Subject: Re: [geda-user] LP1532611 (modular fie formats) fixes
References: <CAC4O8c8tTutWKvXFA-nfcmUiUGYbOY1_5171Vf3WDk09Tmx3yw AT mail DOT gmail DOT com> <56982D5A DOT 1020706 AT prochac DOT sk> <CAC4O8c93jC=qRPAHnzBCrVYONGnyvQ55qv5yQ-vor8es-0_meg AT mail DOT gmail DOT com> <569A2DAC DOT 9070200 AT prochac DOT sk> <569A3280 DOT 3030704 AT iee DOT org>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> http://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/ .

We used that flow before.  Pull requests got lost, a lot of the work
done in forks got forgotten, etc.  We use the same basic flow now
(branch-n-merge instead of fork-n-pull) but having all the "things to
be reviewed" in one spot makes it easier to keep track of it all.

There's nothing stopping you from using the fork model still, as some
of us do.  Just keep in mind that it's your responsibility to keep
your work from being forgotten.

> I'm pretty sure this workflow is not unique to Github, it's just become
> popular because of it.

The details are, though:

"Forking a repository is really straightforward:
    1. Make sure you’re logged into GitHub with your account."

"GitHub makes this part incredibly easy. Once you push a new branch up
 to your repository, GitHub will prompt you to create a pull request"