From: "David S. Miller" <davem@davemloft.net>
To: vsu@altlinux.ru
Cc: git@vger.kernel.org
Subject: Re: weird pull behavior as of late
Date: Mon, 24 Apr 2006 12:46:00 -0700 (PDT) [thread overview]
Message-ID: <20060424.124600.93277140.davem@davemloft.net> (raw)
In-Reply-To: <20060424132922.6e634188.vsu@altlinux.ru>
From: Sergey Vlasov <vsu@altlinux.ru>
Date: Mon, 24 Apr 2006 13:29:22 +0400
> On Sun, 23 Apr 2006 17:59:53 -0700 (PDT) David S. Miller wrote:
>
> > Fast forward
> > MAINTAINERS | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > I got 446 objects and this amounted to just a 4 line change to the
> > MAINTAINERS file? :-)
>
> I got the same problem recently and tracked it down to a stale diff.o
> object file inside libgit.a - apparently "ar rcs" does not recreate the
> archive from scratch. After "make clean" the problem has vanished.
Thanks, I'll give that a try.
prev parent reply other threads:[~2006-04-24 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 0:59 weird pull behavior as of late David S. Miller
2006-04-24 1:18 ` Junio C Hamano
2006-04-24 1:28 ` Kyle McMartin
2006-04-24 9:29 ` Sergey Vlasov
2006-04-24 19:46 ` David S. Miller [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=20060424.124600.93277140.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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).