From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.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 17:10:14 +0100 [thread overview]
Message-ID: <20080123161014.GA5850@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <b0943d9e0801230335m4a2d1855uf465d0d134f3ef39@mail.gmail.com>
On 2008-01-23 11:35:03 +0000, Catalin Marinas wrote:
> On 18/01/2008, Karl Hasselström <kha@treskal.com> wrote:
>
> > The following changes since commit
> > 5b2666bab799830ac5e511f35103d04fc3968b32:
>
> I merged your patches but I have some wishes. Could we keep pretty
> much the same reporting messages? For example, pushing reports a
> conflict but it no longer lists which files conflicted.
Mmm, that's a regression. Will try to see where that got lost.
> 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.
This goes for all commands using the new infrastructure, by the way.
They share a _lot_ of code.
> The pop/push commands report that the action took place. The one
> with "action ... done" was friendlier I think, especially with the
> 'pop' command reporting that it popped the patches but it waits
> quite a lot before returning.
Yes, I agree that the current output is not optimal.
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next prev parent reply other threads:[~2008-01-23 16:13 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 [this message]
2008-01-23 16:42 ` Catalin Marinas
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=20080123161014.GA5850@diana.vm.bytemark.co.uk \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--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).