From: Sean <seanlkml@sympatico.ca>
To: Dave Jones <davej@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: dangling commits.
Date: Sat, 20 May 2006 19:08:02 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP12721518DAEC49D36EF4B8AEA40@CEZ.ICE> (raw)
Message-ID: <20060520190802.0df67730.seanlkml@sympatico.ca> (raw)
In-Reply-To: <20060520230531.GA27511@redhat.com>
On Sat, 20 May 2006 19:05:31 -0400
Dave Jones <davej@redhat.com> wrote:
> What's wrong here?
>
> (tmp)$ mkdir git
> (tmp)$ cd git
> (git)$ rsync -azq rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/git.git/ .git
> (git)$ git-fsck-objects --full
> dangling commit fc024e5e1b92fb11d11aa3c15e9e3f92a888acb6
> dangling commit be49def3dd524b241e3f14c657e740f2e4d73d39
> dangling commit e659abda29b2b25db2771c3e6086f15bc74b1d06
> dangling commit 0f5aaf12d411debc2958dfb029ffcf873d980f15
> dangling commit 8eed8a5da8330df6901f254eab4b7056855b919c
>
> The version of git on that box is 1.2.6-1 from Debian etch.
>
> Dave
>
Nothing wrong. Those commits were just dropped from the "pu" branch at
one time or another when it was rewound. The repository could use a
pruning, but there's no harm done by having those objects remain in
the object database. If you had used any protocol other than rsync,
they would not have appeared in your cloned copy.
Sean
next prev parent reply other threads:[~2006-05-20 23:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 23:05 dangling commits Dave Jones
[not found] ` <20060520190802.0df67730.seanlkml@sympatico.ca>
2006-05-20 23:08 ` Sean [this message]
2006-05-20 23:19 ` Linus Torvalds
2006-05-20 23:49 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-01-15 21:05 Nick Williams
2006-01-15 20:56 ` Andreas Ericsson
2006-01-15 21:37 ` Nick Williams
2006-01-15 21:15 ` Junio C Hamano
2006-01-15 22:11 ` Wolfgang Denk
2006-01-15 22:55 ` Junio C Hamano
2006-01-16 8:52 ` Marco Roeland
2006-01-16 9:27 ` Junio C Hamano
2006-01-16 10:17 ` Marco Roeland
2006-01-16 10:28 ` Andreas Ericsson
2006-01-16 11:33 ` Marco Roeland
2006-01-16 12:05 ` Andreas Ericsson
2006-01-16 12:40 ` Marco Roeland
2006-01-16 9:32 ` Wolfgang Denk
2006-01-16 10:08 ` Marco Roeland
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=BAYC1-PASMTP12721518DAEC49D36EF4B8AEA40@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=davej@redhat.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).