git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: git@vger.kernel.org
Subject: Re: git clone --bare --origin incompatible?
Date: Sun, 23 Oct 2016 14:50:35 +0200	[thread overview]
Message-ID: <20161023125035.GB1486@isis.sigpipe.cz> (raw)
In-Reply-To: <87y41f8czg.fsf@linux-m68k.org>

# schwab@linux-m68k.org / 2016-10-23 14:29:55 +0200:
> On Okt 23 2016, Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> 
> > what is the reason clone --bare prohibits --origin?
> >
> >   % git clone --bare -o fubar anything anywhere
> >   fatal: --bare and --origin fubar options are incompatible.
> 
> Since a bare clone maps remote branches directly to local branches,
> without any remote-tracking branches, --origin doesn't make sense.

is it going to break something though?  i can still go and rename
the remote in the bare repo's config file afterwards.

-- 
roman

      reply	other threads:[~2016-10-23 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-23 11:03 git clone --bare --origin incompatible? Roman Neuhauser
2016-10-23 12:29 ` Andreas Schwab
2016-10-23 12:50   ` Roman Neuhauser [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=20161023125035.GB1486@isis.sigpipe.cz \
    --to=neuhauser@sigpipe.cz \
    --cc=git@vger.kernel.org \
    --cc=schwab@linux-m68k.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).