git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Jeff Brown <jeff@jeffandbetsy.net>
Cc: git@vger.kernel.org
Subject: Re: committing to a checked out branch
Date: Mon, 18 May 2009 22:17:57 -0400	[thread overview]
Message-ID: <76718490905181917u1f41e06dq9cf527a1dac9bea5@mail.gmail.com> (raw)
In-Reply-To: <bbd12f0f0905181733h6a9537d2hf4e6b7a1384fa32d@mail.gmail.com>

On Mon, May 18, 2009 at 8:33 PM, Jeff Brown <jeff@jeffandbetsy.net> wrote:
> The workspace on my server is currently "checked out" so I get the big
> warning message every time I push to there.  What is the best way to
> cleanup that working area so I can push to it without the large
> warning every time I commit.  I know I can set a config variable to
> squelch the message but that isn't what I want to do.  I want to make
> the workspace on the server _not_ be checked out.
>
> Thanks for the help.

If you never want to checkout any branches in that repo on your
server, then what you want is a bare repository. The easiest way to
create it is as follows:

$ git clone --bare /path/to/repo /path/to/repo.git

Then you can remove /path/to/repo after verifying everything is sane.
Note the ".git" extension is a convention denoting the repository is
bare (vs "repo/.git", which implies a repository with a working copy).

j.

  reply	other threads:[~2009-05-19  2:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  0:33 committing to a checked out branch Jeff Brown
2009-05-19  2:17 ` Jay Soffian [this message]
2009-05-19 15:09   ` Jeff Brown
2009-05-19 15:21     ` Jay Soffian
2009-05-19 17:01       ` Jeff Brown

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=76718490905181917u1f41e06dq9cf527a1dac9bea5@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jeff@jeffandbetsy.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;
as well as URLs for NNTP newsgroup(s).