From: Catalin Marinas <catalin.marinas@gmail.com>
To: Jan Veldeman <jan.veldeman@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Stgit - patch history / add extra parents
Date: Fri, 19 Aug 2005 23:15:35 +0100 [thread overview]
Message-ID: <1124489735.6957.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20050819182732.GA5512@fanta>
On Fri, 2005-08-19 at 20:27 +0200, Jan Veldeman wrote:
> hmm, not exactly, for example, when reordering the patches (including the
> top one), I would like to see this in gitk.
> Or when a patch has been dropped (amongst a lot of patches), it should be
> easily spotted.
I tried your patch but the gitk image confused me. I will look again at
it tomorrow (it's quite late in the UK now).
One immediate thing I noticed was that the commits directly accessible
via .git/HEAD are shown as empty by gitk and you would need to follow
the parents to see what they contain. For every freeze, the patches
expand to the right in gitk and the graph could get very complex after
several freeze commands.
--
Catalin
next prev parent reply other threads:[~2005-08-19 22:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 19:57 [RFC] Stgit - patch history / add extra parents Jan Veldeman
2005-08-19 9:53 ` Catalin Marinas
2005-08-19 18:27 ` Jan Veldeman
2005-08-19 22:15 ` Catalin Marinas [this message]
2005-08-19 19:48 ` Jan Veldeman
2005-08-20 21:12 ` Catalin Marinas
2005-08-21 9:40 ` Jan Veldeman
2005-08-22 22:10 ` Daniel Barkalow
2005-08-23 16:55 ` Catalin Marinas
2005-08-23 18:05 ` Daniel Barkalow
2005-08-23 21:23 ` Jan Veldeman
2005-08-23 22:23 ` Daniel Barkalow
2005-08-25 7:09 ` Jan Veldeman
2005-08-25 19:41 ` Daniel Barkalow
2005-08-31 9:27 ` Catalin Marinas
2005-08-31 9:12 ` Catalin Marinas
2005-08-30 21:41 ` Catalin Marinas
2005-08-31 8:59 ` Jan Veldeman
2005-08-31 17:17 ` Daniel Barkalow
2005-08-24 0:23 ` Junio C Hamano
2005-08-24 2:26 ` Linus Torvalds
2005-08-23 1:06 ` 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=1124489735.6957.4.camel@localhost.localdomain \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=jan.veldeman@gmail.com \
/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).