From: Christian Meder <chris@absolutegiganten•org>
To: git@vger•kernel.org
Subject: wit - demo site
Date: Wed, 20 Apr 2005 11:11:32 +0200 [thread overview]
Message-ID: <1113988293.3183.27.camel@localhost> (raw)
Hi,
thanks to my friend Frank Sattelberger I got access to a site where I
could set up a demo for wit:
http://grmso.net:8090
Couple of notes wrt why I work on another git web interface compared
with Kay's work:
* I was already experimenting and implementing for a couple of days when
Kay's tool was first announced and I didn't want to throw away my
feature set
* the Web API: wit has a different philosophy when it comes to URIs: The
stable URI mapping should translate in a straightforward fashion to
git: /blob/<sha1> /tree/<sha1>, /tree/<sha>/diff/<sha1>, etc.; no URL
parameters
* wit is more of a git view right now: it only uses git and tries to
stay close to the repository browsing paradigm (see the API issue above)
* wit provides tarballs and patches but that's an easy one for Kay
* wit looks uglier but that will hopefully change soon ;-)
* I'm a not a Perl guy
I'm still seeking feedback ;-)
Greetings,
Christian
--
Christian Meder, email: chris@absolutegiganten•org
The Way-Seeking Mind of a tenzo is actualized
by rolling up your sleeves.
(Eihei Dogen Zenji)
reply other threads:[~2005-04-20 9:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1113988293.3183.27.camel@localhost \
--to=chris@absolutegiganten$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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