From: Andy Whitcroft <apw@shadowen.org>
To: Git Mailing List <git@vger.kernel.org>
Subject: cvsimport oddness
Date: Sat, 25 Nov 2006 13:33:56 +0000 [thread overview]
Message-ID: <45684644.4040202@shadowen.org> (raw)
skip patchset 2472: 1164219169 before 1164219362
skip patchset 2473: 1164219362 before 1164219362
Generating pack...
Done counting 14014 objects.
Deltifying 14014 objects.
100% (14014/14014) done
Writing 14014 objects.
100% (14014/14014) done
Total 14014, written 14014 (delta 9462), reused 13185 (delta 8872)
Pack pack-aca856ec2fa431ba3bbb975c67ed3a4dd5365a14 created.
DONE.
Already up-to-date.
apw@pinky$
Note that at the end we didn't get any additional revisions or commit
any additional commits. The repack seems excessive in this case.
reply other threads:[~2006-11-25 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45684644.4040202@shadowen.org \
--to=apw@shadowen.org \
--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).