Git development
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: git@vger.kernel.org
Subject: Re: Catching up: git-pasky-0.6.2 broken?
Date: Sat, 23 Apr 2005 18:19:52 +0200	[thread overview]
Message-ID: <1114273192.27940.17.camel@nosferatu.lan> (raw)
In-Reply-To: <20050423152102.D32116@flint.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On Sat, 2005-04-23 at 15:21 +0100, Russell King wrote:
> On Sat, Apr 23, 2005 at 03:12:39PM +0100, Russell King wrote:
> > On Sat, Apr 23, 2005 at 12:47:58PM +0100, Russell King wrote:
> > > 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.
> 
> Ok, don't bother looking into this - I'm now completely git-free here.
> I think I'll prefer to use the old diff and patch method to submit
> stuff to Linus, until git has progressed sufficiently such that it
> doesn't end up wasting hours of my time.
> 
> Yes, it's a radical solution, but since I _can't_ get it to work for
> me, it's the only one which will allow me to get any real work done.
> 
> (and it all looked soo promising pre-0.6.2)
> 

You did try 0.6.3?  Think it fixed some annoying bugs.  Also pull and
reinstall it to make sure one or two others might be fixed.


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-23 16:11 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
2005-04-23 14:21   ` Russell King
2005-04-23 16:19     ` Martin Schlemmer [this message]
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=1114273192.27940.17.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=git@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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