git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: git@vger.kernel.org
Subject: cygwin, 44k files: how to commit only index?
Date: Thu, 7 Dec 2006 15:27:36 +0100	[thread overview]
Message-ID: <81b0412b0612070627r3ff0b394s124d95fbf8084f16@mail.gmail.com> (raw)

I have a kind of awkward project to work with (~44k files, many binaries).

The normal "git commit", which seem to be more than enough
for anything and anyone else, is a really annoying procedure
in my context. It spend too much time refreshing index and
generating list of the files for the commit message.

At first I stopped using git commit -a (doing only update-index),
now I'm about to start using write-tree/commit-tree/update-ref
directly. It helps, but sometimes I really miss -F/-C. It's also
ugly: I can (and almost did) commit an unchanged tree.

Is there any simple way to modify git commit for such a workflow?
Failing that, any simple and _fast_ way to find out if the index

             reply	other threads:[~2006-12-07 14:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 14:27 Alex Riesen [this message]
2006-12-07 19:16 ` cygwin, 44k files: how to commit only index? Junio C Hamano
2006-12-07 19:26   ` Shawn Pearce
2006-12-07 19:35     ` Shawn Pearce
2006-12-07 21:26       ` Christian MICHON
2006-12-09  8:27         ` Torgil Svensson
2006-12-07 19:57     ` Junio C Hamano
2006-12-07 20:29       ` Shawn Pearce
2006-12-07 21:53         ` Junio C Hamano
2006-12-07 22:15   ` Alex Riesen
2006-12-07 22:29     ` Junio C Hamano
2006-12-08  5:27       ` Alex Riesen
2006-12-08  6:54         ` Junio C Hamano
2006-12-08  7:27           ` Alex Riesen
2006-12-08  7:36             ` Junio C Hamano
2006-12-08  7:48               ` Alex Riesen
2006-12-08  8:43             ` Alex Riesen
2006-12-08 14:16     ` Alex Riesen

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=81b0412b0612070627r3ff0b394s124d95fbf8084f16@mail.gmail.com \
    --to=raa.lkml@gmail.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).