git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Jarnbo Pedersen <lars.jarnbo.pedersen@gmail.com>
To: git@vger.kernel.org
Subject: No common commits question
Date: Sat, 14 Jun 2008 11:17:45 +0200	[thread overview]
Message-ID: <1213435065.9800.13.camel@neo> (raw)

Hi,

I have been tracking the Linux kernel with for at least a year now doing
frequent pulls (once every other day or so). I'm not doing any
development so it should be a clean update everytime. However once in a
while I get a "no common commit" warning and git starts to download the
entire repo again. (It happened again today - therefore this mail)

As Im not changing anything I would not expect this to happen, but I may
be wrong. Can anyone explain?

Im using Ubuntu 8.04 using the following version of git and Linux:
- git version 1.5.4.3
- Linux neo 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686
GNU/Linux

Finally I would like to take the opportunity to thank all of you
developers for a GREAT tool. Im currently working as a Software Release
manager and have been working with many of the commercial competitors
and what surprises me about git is that it seems to solve all of the
*BIG* problems you have with SCM in a big corporate environment.
Unfortunately we are NOT using git for the major part of my work, so Im
currently only really enjoing git in my spare time :-)

Regards

Lars Jarnbo Pedersen

             reply	other threads:[~2008-06-14  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  9:17 Lars Jarnbo Pedersen [this message]
2008-06-14  9:29 ` No common commits question Jeff King
2008-06-14 10:09   ` Lars Jarnbo Pedersen

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=1213435065.9800.13.camel@neo \
    --to=lars.jarnbo.pedersen@gmail.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).