From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: Artem Khodush <greenkaa@gmail.com>
Subject: Re: announce: git browser
Date: Mon, 05 Dec 2005 22:53:39 -0800 [thread overview]
Message-ID: <7voe3u67ik.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <40b2b7d90512052240t778f1c8kf182ff065687068c@mail.gmail.com> (Artem Khodush's message of "Tue, 6 Dec 2005 09:40:32 +0300")
Artem Khodush <greenkaa@gmail.com> writes:
>> I see. Well, how useful the big picture is? (Or rather the part of it
>> you don't get by just looking at the current state.)
>
> Yes, I see that for day-to-day development the gitk view is optimal.
> I'll see if I can do something similar, but web-based.
I think there are at least two web interfaces already and this
is the third one with an interesting "twist". Javascript
drawing is cute.
This is not to discourage yet another web based one, but I wish
there were an NNTP interface, that feeds each repository/branch
as a newsgroup and each commit as if it is "git-format-patch"
output, with References: pointing at its parent commit "articles".
A merge commit would probably become a multipart with usually 2
attachments (but N attachments for a N-way octopus), showing
diff from each branch.
next prev parent reply other threads:[~2005-12-06 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 0:23 announce: git browser Artem Khodush
2005-12-05 0:42 ` Petr Baudis
2005-12-05 1:20 ` Artem Khodush
2005-12-05 23:26 ` Petr Baudis
2005-12-06 6:40 ` Artem Khodush
2005-12-06 6:53 ` Junio C Hamano [this message]
2005-12-06 7:31 ` Artem Khodush
2005-12-06 7:45 ` Junio C Hamano
2005-12-06 8:13 ` Artem Khodush
2005-12-06 8:19 ` Junio C Hamano
2005-12-06 8:56 ` Artem Khodush
2005-12-06 9:09 ` Junio C Hamano
2005-12-06 20:23 ` 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=7voe3u67ik.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=greenkaa@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).