From: Steffen Daode Nurpmeso <sdaoden@googlemail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/10] color and pager improvements
Date: Thu, 18 Aug 2011 23:59:53 +0200 [thread overview]
Message-ID: <20110818215953.GA68667@sherwood.local> (raw)
In-Reply-To: <20110818045821.GA17377@sigill.intra.peff.net>
@ Jeff King <peff@peff.net> wrote (2011-08-18 06:58+0200):
> These three fix the problem Steffen mentioned here:
Uuuh, such a shame - you know that it was first noted by
Benjamin Kudria (2008-07-23,
http://marc.info/?l=git&m=121677902502581&w=2).
And it was you who tried to resurrect the same issue last year.
(The thing is: i did not search the archive first because it was
clearly a bug. I did once you referred to your older patch.)
But great that you actually found the time to fix it!
(I must admit though that i'm currently addicted to the coloured
output, because simply switching between my terms gives a clear
indication of where i'm currently git(1)ing. :-> And that in
turn is something which gives more and more fun the longer i use
it! It is *really* fantastic once you get used to it. And do
gc --aggressive and all your temporary fooling is cleaned up.)
Now it's pretty unfortunate that i cannot offer fixes for
anything.
I have a dumb patch of 'rebase -i' which includes the TODO entry
line ($rest) as a comment in the commit message, which is pretty
useful because i think about the rebase task and can store
comments in that very line. But it introduces commit
--cleanup=strip and patches commit.c to add a --message-prefix
option. This is no good yet.
Michael J Gruber's today's shocking exercise on the german
keyboard layout - maybe i should really resurrect parts of that
NBSP series?
And referring to one sentence of yours from the past: no, refspec
stuff *is* that hard: they are not a tree which is created via
'refs_build_tree(); refs_merge_command_line();' upon program
start, with pointers to maybe instantiated .. whatever.
/*
* Note. This is used only by "push"; refspec matching rules for
* push and fetch are subtly different, so do not try to reuse it
* without thinking.
*/
I gave up once i found that (in remote.c). (AFAIR it seems
refspecs are first build L->R, then pushed, then build again but
in R->L direction. Which is why without a fetch= the remotes/
ref is not updated after a push. AFAIK - i gave up ...)
But i'm looking forward and really hope to be able to contribute
some useful and good stuff to great projects in the future.
OpenBSD, for example. :-)
--Steffen
Ciao, sdaoden(*)(gmail.com)
ASCII ribbon campaign ( ) More nuclear fission plants
against HTML e-mail X can serve more coloured
and proprietary attachments / \ and sounding animations
next prev parent reply other threads:[~2011-08-18 22:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 4:58 [PATCH 0/10] color and pager improvements Jeff King
2011-08-18 5:00 ` [PATCH 01/10] t7006: modernize calls to unset Jeff King
2011-08-18 21:05 ` Junio C Hamano
2011-08-18 5:01 ` [PATCH 02/10] test-lib: add helper functions for config Jeff King
2011-08-18 21:10 ` Junio C Hamano
2011-08-18 5:02 ` [PATCH 03/10] t7006: use test_config helpers Jeff King
2011-08-18 5:02 ` [PATCH 04/10] setup_pager: set GIT_PAGER_IN_USE Jeff King
2011-08-18 5:03 ` [PATCH 05/10] diff: refactor COLOR_DIFF from a flag into an int Jeff King
2011-08-18 5:03 ` [PATCH 06/10] git_config_colorbool: refactor stdout_is_tty handling Jeff King
2011-08-18 5:04 ` [PATCH 07/10] color: delay auto-color decision until point of use Jeff King
2011-08-18 21:59 ` Junio C Hamano
2011-08-18 22:28 ` Jeff King
2011-08-18 5:04 ` [PATCH 08/10] config: refactor get_colorbool function Jeff King
2011-08-18 5:05 ` [PATCH 09/10] diff: don't load color config in plumbing Jeff King
2011-08-18 5:05 ` [PATCH 10/10] want_color: automatically fallback to color.ui Jeff King
2011-09-04 2:36 ` Martin von Zweigbergk
2011-09-04 12:53 ` Jeff King
2011-09-05 11:31 ` Steffen Daode Nurpmeso
2011-08-18 21:58 ` [PATCH 0/10] color and pager improvements Jeff King
2011-08-18 21:59 ` [PATCH 11/10] support pager.* for aliases Jeff King
2011-08-18 22:54 ` Junio C Hamano
2011-08-19 3:37 ` Jeff King
2011-08-19 4:18 ` Junio C Hamano
2011-08-19 4:40 ` Jeff King
2011-08-19 5:23 ` Junio C Hamano
2011-08-19 5:43 ` Junio C Hamano
2011-08-19 8:30 ` Jeff King
2011-08-18 22:01 ` [PATCH 12/10] support pager.* for external commands Jeff King
2011-08-18 22:56 ` Junio C Hamano
2012-02-12 0:46 ` Ævar Arnfjörð Bjarmason
2012-02-14 19:13 ` Jeff King
2011-08-18 22:33 ` [PATCH 0/10] color and pager improvements Ingo Brückl
2011-08-18 22:46 ` Jeff King
2011-08-19 6:34 ` Ingo Brückl
2011-08-25 20:25 ` Jeff King
2011-08-18 21:59 ` Steffen Daode Nurpmeso [this message]
2011-08-18 22:02 ` Junio C Hamano
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=20110818215953.GA68667@sherwood.local \
--to=sdaoden@googlemail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).