All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: git@vger.kernel.org
Subject: Re: Catching up: git-pasky-0.6.2 broken?
Date: Sat, 23 Apr 2005 15:12:39 +0100	[thread overview]
Message-ID: <20050423151238.C32116@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050423124758.B32116@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Sat, Apr 23, 2005 at 12:47:58PM +0100

On Sat, Apr 23, 2005 at 12:47:58PM +0100, Russell King wrote:
> I've been away from git stuff since about Wednesday due to eye problems.
> Yesterday and today, I've been trying to catch up, but I'm running into
> problems.
> 
> I grabbed git-pasky-0.6.2, and followed Linus' message about converting
> repositories.  I've updated all the "heads", and cleaned out all the old
> sha1 files.  After updating, I did a read-tree for the tracked head,
> followed by checkout-cache -f -a and update-cache --refresh.
> 
> Therefore, in theory, everything should be in sync.
> 
> However, git pull now has nasty side effects.  At first I thought this
> was down to something still being out of sync.  However, on the second
> pull, it's still producing the same complaints.
> 
> It's almost although git has a single patch file subversely written into
> it to apply lpfc and qla changes which it's trying to apply irrespective
> of the objects downloaded.
> 
> Any ideas what's going on?

Could the problem be related to some random garbage left in .git/add-queue
and .git/rm-queue?

If so, how did these files get generated in the first place, and why
weren't they removed when they were finished with?

IMHO updating a repository from an external source should _NOT_ be
affected by the presence (or absense) of these two files, which
contain only _local_ state information.

-- 
Russell King


  reply	other threads:[~2005-04-23 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23 11:47 Catching up: git-pasky-0.6.2 broken? Russell King
2005-04-23 14:12 ` Russell King [this message]
2005-04-23 14:21   ` Russell King
2005-04-23 16:19     ` Martin Schlemmer
2005-04-23 21:25   ` Petr Baudis

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=20050423151238.C32116@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.