From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Adam Simpkins <adam@adamsimpkins.net>
Cc: Teemu Likonen <tlikonen@iki.fi>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: Unresolved issues, "log --graph"
Date: Mon, 21 Apr 2008 18:59:28 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0804211859100.2298@eeepc-johanness> (raw)
In-Reply-To: <20080421173312.GA18367@adamsimpkins.net>
Hi,
On Mon, 21 Apr 2008, Adam Simpkins wrote:
> On Sun, Apr 20, 2008 at 06:48:48PM +0300, Teemu Likonen wrote:
> > Junio C Hamano wrote (2008-04-19 01:19 -0700):
> >
> > > Here is an "issues" list I am keeping track of on the back of my head
> > > (and in "TODO" file on 'todo' branch, which is not updated often
> > > enough).
> >
> > > * log --graph (Adam Simpkins)
> >
> > Hi Adam, any changes for modifying the "log --graph" patch series to
> > make it apply to the current development version of git? It would just
> > feel wrong if this apparently well-designed tool was left behind. Of
> > course it's up to you.
>
> Yes. I didn't mean to drop this, I've just haven't had much time to
> work on it lately. I may get a chance to work on it tomorrow,
> otherwise I'll do it this coming weekend.
>
> I'll submit a new series of patches to apply the "log --graph" changes
> onto master. I think the only thing that needs to be changed is to
> update my code to work with Junio's jc/terminator-separator changes.
> It looks like it should be fairly straightforward.
>
> Junio and others, is there anything else I should do to make the "log
> --graph" changes ready for pu/next/master?
I look forward to it!
Ciao,
Dscho
prev parent reply other threads:[~2008-04-21 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 8:19 Unresolved issues Junio C Hamano
2008-04-20 15:48 ` Unresolved issues, "log --graph" Teemu Likonen
2008-04-21 17:33 ` Adam Simpkins
2008-04-21 17:59 ` Johannes Schindelin [this message]
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=alpine.DEB.1.00.0804211859100.2298@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tlikonen@iki.fi \
/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