git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Peter Oberndorfer" <kumbayo84@arcor.de>,
	git@vger.kernel.org, "Pavel Roskin" <proski@gnu.org>
Subject: Re: [STGIT PATCH] replace "git repo-config" usage by "git config"
Date: Wed, 23 Jan 2008 16:42:41 +0000	[thread overview]
Message-ID: <b0943d9e0801230842w250ab963t16a1ab3c8024487e@mail.gmail.com> (raw)
In-Reply-To: <20080123161014.GA5850@diana.vm.bytemark.co.uk>

On 23/01/2008, Karl Hasselström <kha@treskal.com> wrote:
> On 2008-01-23 11:35:03 +0000, Catalin Marinas wrote:
> > The 'goto' checks the local status before pushing but doesn't report
> > this (and my machine is slow and it might wait even 20 seconds or
> > more, it is useful to get some messages).
>
> No, it doesn't anymore, so it should be faster than before. Instead of
> checking the entire tree for cleanliness, it just relies on
> git-read-tree -u -m to abort without changes if any of the files that
> need updating are dirty.

Ah, OK. BTW, even if the tree was clean, a 'goto' failed on my Linux
tree earlier today with the following message:

$ stg goto realview-eb-header
Popped realview-pb1176 -- realview-ioaddress
fatal: Entry 'arch/arm/mach-realview/realview_pb11mp.c' not uptodate.
Cannot merge.
stg goto: Command aborted (all changes rolled back)

It worked fine after running 'stg status' once (and not showing any
changes). In the old GIT interface, we use to call refresh_index (i.e.
'git update-index -q --unmerged --refresh'). Does this still happen?

The message above also shows what I meant with messages not being very
clear. It reports "Popped" but actually failed. Showing "Popping ...
done" would be better.

-- 
Catalin

  reply	other threads:[~2008-01-23 16:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16  3:19 [RFC/PATCH] Remove repo-config Dan McGee
2008-01-16  4:23 ` Junio C Hamano
2008-01-16  4:40   ` Dan McGee
2008-01-16 17:20     ` Junio C Hamano
2008-01-16 20:32       ` Junio C Hamano
2008-01-16 20:13 ` Junio C Hamano
2008-01-16 20:47 ` Peter Oberndorfer
2008-01-16 20:58   ` [STGIT PATCH] replace "git repo-config" usage by "git config" Peter Oberndorfer
2008-01-16 21:13     ` Jakub Narebski
2008-01-16 21:46       ` Peter Oberndorfer
2008-01-17 17:07       ` Catalin Marinas
2008-01-17 23:49         ` Jakub Narebski
2008-01-17  7:45     ` Karl Hasselström
2008-01-18  4:24       ` Karl Hasselström
2008-01-23 11:35         ` Catalin Marinas
2008-01-23 16:10           ` Karl Hasselström
2008-01-23 16:42             ` Catalin Marinas [this message]
2008-01-24  7:01               ` Karl Hasselström
2008-01-24 15:31                 ` Catalin Marinas
2008-01-24 18:08                   ` Karl Hasselström
2008-01-24 18:20                     ` Catalin Marinas

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=b0943d9e0801230842w250ab963t16a1ab3c8024487e@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    --cc=kumbayo84@arcor.de \
    --cc=proski@gnu.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).