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

Re: bare vs non-bare <1.7 then >=1.7 ?

From
Jeff King <peff@peff.net>
Date
Nov 8, 2012, 14:59 UTC
Message-ID
<20121108145951.GA15560@sigill.intra.peff.net>
In-Reply-To
<87zk2sz0mn.fsf@flaca.cmartin.tk>
On Thu, Nov 08, 2012 at 02:26:40PM +0100, Carlos Martín Nieto wrote:
Show 14 quoted lines
> > When experimenting in order to train some colleagues, I saw that If I
> > clone a repository, I couldn't push to it because it was a non-bare
> > one.
> > Searchin for some explanations, I found this ressource:
> > http://www.bitflop.com/document/111
> >
> > It's told to be reliable information for Git < v1.7.
> >
> > What would be different for Git > 1.7 so that I could be up to date
> > with the facts?
> 
> Bare vs. non-bare hasn't changed. The reasoning behind the two types
> hasn't changed and is pretty fundamental. There is no reason for it to
> change.

Right. The key thing that changed in git v1.7 is that we started warning about and denying an operation that had always been dangerous, and that is why the referenced document mentions that version.

-Peff
Previous: Carlos Martin NietoNext: Enrico Weigelt
Message 3 of 5 in “bare vs non-bare <1.7 then >=1.7 ?”
  1. Mihamina RakotomandimbyNov 8, 2012
  2. Carlos Martin NietoNov 8, 2012
  3. Jeff KingNov 8, 2012
  4. Enrico WeigeltNov 10, 2012
  5. Philip OakleyNov 10, 2012

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.