From: "Doug Reiland" <dreiland@gmail.com>
To: git@vger.kernel.org
Subject: git and branches newie questions
Date: Thu, 2 Nov 2006 12:02:42 -0500 [thread overview]
Message-ID: <6844644e0611020902tc6251f7i2eda0d3fc82e0502@mail.gmail.com> (raw)
I need some suggestions for the best way to setup my repositories.
I have a linux repository cloned right from Linus.
I want to create 2 additional branches in this repository:
internal_current and internal_testing
I want to use internal_current to make modifications to the main Linux
branch for an internal project.
I want other users to clone/pull/push changes to the internal_current branch.
I want to use internal_testing as a branch to merge and test the
latest Linux branch with changes made to internal_current. Once this
testing is complete, merge the changes into internal_current.
That is the best way to do this. I am open to use cogito. I have
messed up this merging process just about each time, and I want to get
a stable process before I open this up to other users.
Also, I can't figure out permissions. I have setup the allow_users
hook in .git/hooks/update. My repository is "owned" by gate_keeper. My
user login is dreiland. I push changes back to the gate_keeper
repository and stuff under .git gets owned by me. Now, I log as a
gate_keeper to get a Linus update or perform the internal_testing
merges and things fail because it is owned by dreiland.
next reply other threads:[~2006-11-02 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 17:02 Doug Reiland [this message]
2006-11-04 7:46 ` git and branches newie questions Alan Chandler
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=6844644e0611020902tc6251f7i2eda0d3fc82e0502@mail.gmail.com \
--to=dreiland@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).