# git clone --bare --origin incompatible?

3 messages from 2016-10-23 to 2016-10-23. Participants: Roman Neuhauser, Andreas Schwab.
Thread: https://gitlist.dev/t/44362

## Roman Neuhauser, 2016-10-23 11:03

Subject: git clone --bare --origin incompatible?
Message-ID: <20161023110338.GA1486@isis.sigpipe.cz>
URL: https://gitlist.dev/e/20161023110338.GA1486%40isis.sigpipe.cz

```
hello,

what is the reason clone --bare prohibits --origin?

  % git clone --bare -o fubar anything anywhere
  fatal: --bare and --origin fubar options are incompatible.


-- 
roman

```

## Andreas Schwab, 2016-10-23 12:29

Subject: Re: git clone --bare --origin incompatible?
Message-ID: <87y41f8czg.fsf@linux-m68k.org>
URL: https://gitlist.dev/e/87y41f8czg.fsf%40linux-m68k.org
In-Reply-To: <20161023110338.GA1486@isis.sigpipe.cz>

```
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.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

```

## Roman Neuhauser, 2016-10-23 12:50

Subject: Re: git clone --bare --origin incompatible?
Message-ID: <20161023125035.GB1486@isis.sigpipe.cz>
URL: https://gitlist.dev/e/20161023125035.GB1486%40isis.sigpipe.cz
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

```
