git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommi Virtanen <tv@eagain.net>
To: "Сергей Шарыбин" <nazgul@school9.perm.ru>
Cc: git@vger.kernel.org
Subject: Re: pre-commit hook, non-zero exit status and dangling objects
Date: Mon, 25 Aug 2008 16:35:27 +0300	[thread overview]
Message-ID: <20080825133527.GD14930@eagain.net> (raw)
In-Reply-To: <48B13EB0.8050704@school9.perm.ru>

On Sun, Aug 24, 2008 at 04:57:52PM +0600, Сергей Шарыбин wrote:
> After pre-commit returned non-zero status, I could see new dangling  
> objects in my repo. I think it's not normal, because pre-commit is often  
> used for checking formation of source files and after changing this  
> files, hash of object will be also changed and even after successfull  
> commit dangling object will be still alive.

You also get dangling objects by running git add. There's no harm in
them, they will be cleaned up automatically.

-- 
:(){ :|:&};:

      reply	other threads:[~2008-08-25 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 10:57 pre-commit hook, non-zero exit status and dangling objects Сергей Шарыбин
2008-08-25 13:35 ` Tommi Virtanen [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=20080825133527.GD14930@eagain.net \
    --to=tv@eagain.net \
    --cc=git@vger.kernel.org \
    --cc=nazgul@school9.perm.ru \
    /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).