Re: committing to a checked out branch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 18, 2009 at 8:33 PM, Jeff Brown <jeff@xxxxxxxxxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]