git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy O'Brien <obrien654j@gmail.com>
To: git@vger.kernel.org
Subject: A usage question
Date: Sat, 30 May 2009 23:34:31 -0400	[thread overview]
Message-ID: <20090531033431.GB25869@darkbox> (raw)

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

Hello,

I have a git usage question. I'm working on three separate branches in a
foreign SCM called Surround. One branch is the mainline, and two others
are a v1 branch based off the mainline and the other is a v2 branch
based off the mainline with many new features that we hope to release
soon. Some components of the v1 branch are similar, but not identical to
the v2 branch, and other parts are completely different. I am primarily
working on the v2 branch, but some things that I change can/should be
backported to the v1 and mainline branches.

The foreign SCM requires one working directory for each branch, so I
currently have three separate git repos with the contents of what is on
Surround for each, and then I have one "local" git repo that I'm using
to do my development. I have three branches on this local repo: one to
track each git repo set up for Surround. I've been using topic branches
in my local dev repo to do my work, and then merging my changes into the
branch I branched my topic branch from, and cherry-picking ones into the
other two branches that could be used there. I then push these branches
to the repos and check then into Surround when I am ready to. This
doesn't seem efficient to me at all, and I was wondering if there is a
better setup someone could suggest that would make development easier.
Sorry for the huge message.

Thanks for any suggestions.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-05-31  3:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31  3:34 Jeremy O'Brien [this message]
2009-06-01 16:32 ` A usage question Daniel Barkalow

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=20090531033431.GB25869@darkbox \
    --to=obrien654j@gmail.com \
    --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.
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).