git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Constantine Plotnikov <constantine.plotnikov@gmail.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: spearce@spearce.org, git@vger.kernel.org
Subject: Re: [JGIT PATCH] Added support for creating bare repositories
Date: Mon, 27 Apr 2009 16:46:03 +0400	[thread overview]
Message-ID: <85647ef50904270546w41692a50j84cc898a264998ba@mail.gmail.com> (raw)
In-Reply-To: <200904270029.56939.robin.rosenberg.lists@dewire.com>

On Mon, Apr 27, 2009 at 2:29 AM, Robin Rosenberg
<robin.rosenberg.lists@dewire.com> wrote:
> fredag 24 april 2009 17:36:57 skrev Constantine Plotnikov <constantine.plotnikov@gmail.com>:
>> Now it is possible to create bare repositories.
>> The difference from normal repository creation is
>> that directory where repository is created might
>> exists and that core.bare property is set to true.
>
> I know C Git doesn't check if a directory is a non-bare repo, but I think
> that's wrong, so if I try to create a bare repo in a non-bare repo that
> should be an error. For now I'll accept it anyway since the C version allows
> it and it is useful.
>
I'm not sure that this should be an error. We have a bare git
repository with a test data inside the non-bare repository. And such
feature might be nice to have to other git related tools as well. %)

Constantine

      reply	other threads:[~2009-04-27 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 15:36 [JGIT PATCH] Added support for creating bare repositories Constantine Plotnikov
2009-04-26 22:29 ` Robin Rosenberg
2009-04-27 12:46   ` Constantine Plotnikov [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=85647ef50904270546w41692a50j84cc898a264998ba@mail.gmail.com \
    --to=constantine.plotnikov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    --cc=spearce@spearce.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).