git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* git clone --bare --origin incompatible?
@ 2016-10-23 11:03 Roman Neuhauser
  2016-10-23 12:29 ` Andreas Schwab
  0 siblings, 1 reply; 3+ messages in thread
From: Roman Neuhauser @ 2016-10-23 11:03 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git clone --bare --origin incompatible?
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Andreas Schwab @ 2016-10-23 12:29 UTC (permalink / raw)
  To: Roman Neuhauser; +Cc: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: git clone --bare --origin incompatible?
  2016-10-23 12:29 ` Andreas Schwab
@ 2016-10-23 12:50   ` Roman Neuhauser
  0 siblings, 0 replies; 3+ messages in thread
From: Roman Neuhauser @ 2016-10-23 12:50 UTC (permalink / raw)
  To: Andreas Schwab; +Cc: git

# 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-10-23 12:50 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).