git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git clone --bare --origin incompatible?

From
RNRoman Neuhauser <neuhauser@sigpipe.cz>
Date
Oct 23, 2016, 12:50 UTC
Message-ID
<20161023125035.GB1486@isis.sigpipe.cz>
In-Reply-To
<87y41f8czg.fsf@linux-m68k.org>
# schwab@linux-m68k.org / 2016-10-23 14:29:55 +0200:
Show 9 quoted lines
> 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
Previous: Andreas Schwab
Message 3 of 3 in “git clone --bare --origin incompatible?”
  1. Roman NeuhauserOct 23, 2016
  2. Andreas SchwabOct 23, 2016
  3. Roman NeuhauserOct 23, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.