git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Davies <aaron.davies@gmail.com>
To: git@vger.kernel.org
Subject: newb questions: post-cherry-pick status cleanup, shared local  repository permissions
Date: Mon, 30 Mar 2009 11:03:28 +0800	[thread overview]
Message-ID: <c4e763ac0903292003j22934e7ax9f9ae986bdcd6abb@mail.gmail.com> (raw)

hi, i'm new to git, and have a couple questions which are probably
very stupid and/or indicate that i've been doing it wrong.

first, a couple words about my setup/workflow: i'm currently sole
developer on a project which may at some point get some other coders.
the environment is three linux boxes, one for development and two for
production, and three accounts, mine, dev, and prod. all homedirs are
hosted on the network and are accessible from all three boxen.

i have a "central" (i.e. bare) repository stored in dev's homedir, and
regular copies in all three homedirs. the language involved is
interpreted, so the code tree is the deployment.

my main workflow is to hack on a branch in my homedir, then merge and
push when i have a feature ready. then i go to the dev account and
pull, which constitutes dev deployment. once it's thoroughly tested, i
do the same in the prod account.

now, the questions: an exception to this workflow occurred a couple
months ago, when i made some urgent bugfixes that needed to move to
prod before other stuff that was currently being tested in dev. this
was done via cherry-picking some specific commits into prod. now, in
prod, when i do "git status", it says "# Your branch is ahead of
'origin/master' by 8 commits." is there an easy way to get rid of
this? last time i tried it on my own, i attempted some sort of push
from prod back to dev, wiped out most of the changes since those
cherry-picks, and had to recover by restoring my repository from
backup.

second, the ownership structure i currently have for the "central"
repository feels wrong to me--the whole thing is owned by my personal
account, depsite being hosted in dev's account. since i'm the only one
who ever pushes into it, this is not currently a problem, but it's
caused permissions issues on the rare occasions i've tried to push
from other accounts (e.g. prod, above), and will presumably cause many
more if anyone else ever starts coding on this project.

advice?
-- 
Aaron Davies
aaron.davies@gmail.com

             reply	other threads:[~2009-03-30  3:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  3:03 Aaron Davies [this message]
2009-03-30  4:22 ` newb questions: post-cherry-pick status cleanup, shared local repository permissions Nicolas Sebrecht
2009-03-30  4:30   ` Nicolas Sebrecht

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=c4e763ac0903292003j22934e7ax9f9ae986bdcd6abb@mail.gmail.com \
    --to=aaron.davies@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).