From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: git@vger.kernel.org
Subject: Re: Safe to interrupt »git gc --auto«?
Date: Wed, 29 Oct 2014 13:50:51 -0700 [thread overview]
Message-ID: <20141029205051.GK5500@google.com> (raw)
In-Reply-To: <87fve6gbk3.fsf@kepler.schwinge.homeip.net>
Thomas Schwinge wrote:
> I couldn't find this answered in the documentation: if, instead of
> exiting right away, a »git gc --auto« actually commences its housekeeping
> tasks, is it safe to interrupt (C-c, SIGINT) the original git invocation
> at this point, or might this cause any inconsistencies, data loss,
[...]
Heh.
If gc --auto happens in the middle of e.g. a rebase, then it's possible
that there were more commits that were supposed to happen later. You'd
need to run 'git rebase --continue' after interrupting the gc in that
case.
Interruption should never cause data loss, and as much as possible
commands should finish their work before running gc --auto. Please
let us know if some command is violating that.
Thanks,
Jonathan
prev parent reply other threads:[~2014-10-29 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 15:06 Safe to interrupt »git gc --auto«? Thomas Schwinge
2014-10-29 20:50 ` Jonathan Nieder [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=20141029205051.GK5500@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=thomas@codesourcery.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).