git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Arnauld Van Muysewinkel <arnauldvm@gmail.com>, git@vger.kernel.org
Subject: Re: [QUESTION] or [BUG] Could not stash new bin files
Date: Mon, 19 Apr 2010 08:41:17 -0400	[thread overview]
Message-ID: <20100419124117.GA20184@coredump.intra.peff.net> (raw)
In-Reply-To: <20100419093523.GA26342@progeny.tock>

On Mon, Apr 19, 2010 at 04:35:23AM -0500, Jonathan Nieder wrote:

> >     $ git add -N XXX/src/jrxml/*.xls
> >     $ git stash save --keep-index "Improving performance of views"
> >     XXX/src/jrxml/SubCellMatrixCompared-EXPLAIN-new.xls: not added yet
> >     XXX/src/jrxml/SubCellMatrixCompared-EXPLAIN-old.xls: not added yet
> >     fatal: git-write-tree: error building trees
> 
> Yes, this is a known problem [1].

Thanks for the pointer.

Re-reading that thread, and considering the fact that this comes up so
rarely, I think leaving it as an error is fine. We could possibly give a
bit more advice on how to proceed, though.

> > Specificities:
> > 
> > * I have a file in the index that I do not want to stash
> 
> Could you explain this further?  The stash currently saves everything
> about the current state (except files not in the index nor HEAD).

Yeah, I'm not really sure why intent-to-add is being used here at all,
instead of regular "git add".

But if the real problem is wanting to stash part of your changes, then
the best thing is probably to use the interactive "git stash -p".

> > * The two new files are binary files

I don't think that is relevant here. The intent-to-add bit is the
problem.

-Peff

      reply	other threads:[~2010-04-19 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  8:19 [QUESTION] or [BUG] Could not stash new bin files Arnauld Van Muysewinkel
2010-04-19  9:35 ` Jonathan Nieder
2010-04-19 12:41   ` Jeff King [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=20100419124117.GA20184@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=arnauldvm@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    /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).