From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Tommy Wang <subscription@august8.net>
Cc: git <git@vger.kernel.org>, Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Git & Project Workflow
Date: Fri, 6 Nov 2009 22:44:53 +0100 [thread overview]
Message-ID: <20091106214452.GA13724@vidovic> (raw)
In-Reply-To: <ae09c2a40911051619s36c9a781pdb403fb9140affdf@mail.gmail.com>
The 05/11/09, Tommy Wang wrote:
> Hi,
Hi,
> it takes considerably more time to look through a list of
> commits, and pick out the ones that can be moved from main -> limited.
Instead of doing this massive (time consuming) cherry-picking, why don't
you avoid the whole "main -> limited" workflow ? This looks a bit ugly
for me.
I think that the main developers should work by default with the limited
repo and only commit for the secret files into main. This would result
in only pulling limited work into main ("limited -> main" workflow).
Let's rename main to secret and limited to normal to have the semantic
stick with my point. In this case, whole developers work with normal for
the "normal" tasks. If they need a secret change, secret developers
commit and push to secret. Then, you only need to pull normal from
secret and resolve conflicts in one place.
--
Nicolas Sebrecht
prev parent reply other threads:[~2009-11-06 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 0:19 Git & Project Workflow Tommy Wang
2009-11-06 21:44 ` Nicolas Sebrecht [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=20091106214452.GA13724@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=git@vger.kernel.org \
--cc=subscription@august8.net \
/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