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

Re: [PATCH] filter-branch: really allow running in a bare repository

From
EKEric Kidd <emk.lists@randomhacks.net>
Date
Feb 3, 2009, 19:31 UTC
Message-ID
<431341160902031131s63f34665ne9db25d8a4d1f0f9@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0902031910001.9822@pacific.mpi-cbg.de>

On Tue, Feb 3, 2009 at 1:10 PM, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:

> When checking if running in a bare repository, the work tree has to be
> reset, otherwise we will be checking the temporary state, which is
> always non-bare.

Just a few minutes after you posted this patch, I posted a nearly-identical fix for the same issue:

  http://marc.info/?l=git&m=123368695831812&w=2
(My patch includes a test case, too, but it's not very important.)

This raises another interesting question: Why doesn't 'git filter-branch' actually check whether subcommands succeed?

Cheers, Eric

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 2 of 4 in “filter-branch: really allow running in a bare repository”
  1. filter-branch: really allow running in a bare repositoryJohannes Schindelin, Feb 3, 2009
  2. Eric KiddFeb 3, 2009
  3. Johannes SchindelinFeb 3, 2009
  4. Eric KiddFeb 3, 2009

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.