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

Re: [PATCH] Fix "git submodule status" output when "git describe" is not possible

From
ABAlberto Bertogli <albertito@gmail.com>
Date
Feb 24, 2008, 20:49 UTC
Message-ID
<20080224204939.GE10119@gmail.com>
In-Reply-To
<7vprv1zn27.fsf@gitster.siamese.dyndns.org>
On Tue, Feb 12, 2008 at 05:01:52PM -0800, Junio C Hamano wrote:
Show 7 quoted lines
> Alberto Bertogli <albertito@gmail.com> writes:
> 
> > When a submodule cannot be described, doing a "git submodule status" on
> > the supermodule produces unnecesary and scary output,...
> 
> I had an impression that describe got a new feature for a case
> like this recently.

I'm sorry but I've read the docs and tried with a few options and I have no idea what that one may be.

The bug is still present on 'next' as of an hour ago.
Thanks,
		Alberto
Previous: Junio C Hamano
Message 3 of 3 in “Fix "git submodule status" output when "git describe" is not possible”
  1. Fix "git submodule status" output when "git describe" is not possibleAlberto Bertogli, Feb 13, 2008
  2. Junio C HamanoFeb 13, 2008
  3. Alberto BertogliFeb 24, 2008

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.