git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: "Sean B. Palmer" <sean@miscoranda.com>
Cc: git@vger.kernel.org
Subject: Re: Deleting a Bare Repo
Date: Fri, 18 Mar 2011 16:36:41 -0500	[thread overview]
Message-ID: <4D83D069.1050206@gmail.com> (raw)
In-Reply-To: <AANLkTimaQ3dyXDJgY_Ys19jpNXx07vK2qNLQ_8Cp8NKi@mail.gmail.com>

On 3/18/2011 10:26 AM, Sean B. Palmer wrote:
> I'd like to delete a bare git repo, but I want to check that (a) it's
> being used as the actual git bare repo, e.g. if $GIT_DIR is set, and
> (b) that it is actually a git repo. Using rm -rf .git/ doesn't seem
> safe for these reasons, so is there a command in git itself to do
> this?
>
> I've been going through the man pages without success.
>
here is a partial list of considerations and inqueries:
* there is not a git command to delete a repo.  rm -rf is how you do it.
* git repo's are not aware of who has cloned from them and/or is 
pulling/fetching from them.
* if there is a git-daemon-export-ok then that means it was setup to be 
pull-from via the git:// protocol.  however, that doesn't mean anyone is 
actually pulling from it.
* check the config file and see if its setup as a mirror.  if so, 
investigate its mirror.

if you are talking about manual deletion you could:
* cd to the bare repo and do a git-status.  if it returns a status then 
it's a working repo (not necessarily a referenced repo).
* analyze it in gitk and see if anyone has pushed to it recently.
* rename it and see if anyone complains.

v/r,
neal

      reply	other threads:[~2011-03-18 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 15:26 Deleting a Bare Repo Sean B. Palmer
2011-03-18 21:36 ` Neal Kreitzinger [this message]

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=4D83D069.1050206@gmail.com \
    --to=nkreitzinger@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sean@miscoranda.com \
    /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).