git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Patrick Neuner <neuner@futureweb.at>
To: git@vger.kernel.org
Subject: Parallell Development / Switching to GIT
Date: Thu, 25 Jun 2009 09:52:06 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090625T095000-90@post.gmane.org> (raw)

Hello,

we are using SVN right now and with the way we do / need to develop, it seems we
are constantly get in a merging horror. 
I did quite some reading about git now, but I am still not really sure if that
what we try to accomplish can be done with git,
Or if we are really doing something a too odd way. 

Let my try to describe – I also added an image. 

---- repo 1
  |
   - repo 2 (=branch of repo 1 - for our external developers)

We have the main branch and 2nd branch for external developers. 

We work inside the repo1, which are usually features/updates that go life after
a short turn. 
Our external developer work on different features that will be merged into repo1
from time to time. 

Usually during development, we sometimes need to push features from repo1 to
repo2, and later the features developed on repo2 will be pushed back to repo1, 
And also smaller bug fixes come from repo2 that needs to go into repo1. 

But this is a constant process, meaning, that both branches will exist,
especially repo2 will exist after this feature has finished for smaller
updates/bugfixes. 
We don’t want to do a new branch for each bugfix, for each new small feature,
but have different branches for different developer teams. 

So I was wondering, if this could cause troubles with GIT in case of merging
around without closing a branch. 

I am adding an link to an image that might show what I tried to explain. 
http://temp.in.futureweb.at/parallell-development.png

Thanks
Patrick

             reply	other threads:[~2009-06-25  9:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25  9:52 Patrick Neuner [this message]
2009-06-25 10:11 ` Parallell Development / Switching to GIT Andreas Ericsson
2009-06-28 17:51   ` AW: " Patrick Neuner - Futureweb.at
2009-06-28 18:47     ` Jeff King
2009-06-28 20:08       ` AW: " Patrick Neuner - Futureweb.at
2009-06-28 22:33         ` David Aguilar
2009-06-29  8:35         ` AW: " Andreas Ericsson
2009-06-29 16:37           ` Peter Harris
2009-07-02  0:47           ` AW: " Patrick Neuner - Futureweb.at
2009-07-02  6:20             ` Johannes Sixt
2009-07-02 11:44               ` AW: " Patrick Neuner - Futureweb.at
2009-07-02 11:55                 ` Johannes Sixt
2009-06-30  5:32         ` Jeff King

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20090625T095000-90@post.gmane.org \
    --to=neuner@futureweb.at \
    --cc=git@vger.kernel.org \
    /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://80x24.org/mirrors/git.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).