git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Dave Abrahams <dave@boostpro.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [bug] submodule --update insufficiently verbose
Date: Tue, 10 Jan 2012 11:43:24 +0100	[thread overview]
Message-ID: <87k44zj0s3.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <m239bqnctf.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Sat, 07 Jan 2012 21:33:00 -0500")

Dave Abrahams <dave@boostpro.com> writes:

> When a "git submodule --update" fails, e.g., due to a dirty working
> directory in one of the submodules, nothing is printed out indicating
> the submodule or directory in which the failure occurred.  This seems
> like a usability bug to me.

I assume you mean 'git submodule update'.  What git version is this, and
how do you reproduce?  I get a message like

  error: Your local changes to the following files would be overwritten by checkout:
          foo
  Please, commit your changes or stash them before you can switch branches.
  Aborting
  Unable to checkout '1fac3675a8c65b14e0a98e0136b5c43db97706fe' in submodule path 'sub'

in a simple test.  I am using a development version, but a brief glance
at the history seems to indictate that the 'Unable to ... in submodule
...' has always been there.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

      reply	other threads:[~2012-01-10 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08  2:33 [bug] submodule --update insufficiently verbose Dave Abrahams
2012-01-10 10:43 ` Thomas Rast [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k44zj0s3.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=dave@boostpro.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).