git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: walt <wa1ter@myrealbox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: Problem with Linus's git repository?
Date: Fri, 29 Jun 2007 15:00:09 +0200	[thread overview]
Message-ID: <46850259.8030708@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0706290537130.7055@x2.ybpnyarg>

walt wrote:
> 
> On Thu, 28 Jun 2007, Linus Torvalds wrote:
> 
>> On Thu, 28 Jun 2007, walt wrote:
>>> No, every morning I pull from you and Junio and Petr Baudis using cg-update,
> 
> 
>> Oh, don't use "cg-update", or just fix it to do "git pull".
> 
> I'm happy to stick with using git.  From reading the latest Docs, it seems
> that git-pull -v will do what I need (I think).
> 
> That's what I did just now to update from you and Junio, and the output
> seemed exactly appropriate -- ended with a fast-forward and no errors
> for either one.
> 
> However, a git-fsck turned up four dangling commits for Junio, and 42
> danglers for you, including a mix of blobs, trees, and commits.
> 

You will see dangling commits, blobs and trees from Junio because he rewinds
his 'pu' branch.

I'm not sure why you see any from Linus, as I'm not aware of any rewinding
in the official kernel tree (unless you're talking about some other repo,
in which case I'm clueless).

> Will a simple git-prune bring me correctly up to date, or am I missing
> some steps?
> 

You're already up to date. The dangling commits do not hurt your repo
in any way. Nor do they hurt the performance of any of the tools you
normally use. fsck suffers a bit from them, because it has to care
about them, but the normal DAG-traversing tools will never even
see them.

git prune would remove them and save you a tiny bit of diskspace.
Next time you pull from Junio, you'll most likely get orphaned commits
again though, meaning blobs, trees and commits will end up dangling once
more. It's perfectly normal and nothing to worry about.

For repo maintenance, I run "git gc" once a month on my local copies.
More to let my laptop do something while I'm fiddling with receipts and
stuff than for any real need (the idea of idle computers offend me for
some reason).

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

      reply	other threads:[~2007-06-29 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26 14:45 Problem with Linus's git repository? walt
2007-06-26 16:43 ` Linus Torvalds
2007-06-27 13:41   ` walt
2007-06-27 16:34     ` Linus Torvalds
2007-06-28  4:19       ` Junio C Hamano
2007-06-28 13:37       ` walt
2007-06-28 15:20         ` Johannes Schindelin
2007-06-28 15:41         ` Linus Torvalds
2007-06-29 12:47           ` walt
2007-06-29 13:00             ` Andreas Ericsson [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=46850259.8030708@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wa1ter@myrealbox.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).