From: Thomas Gleixner <tglx@linutronix.de>
To: git@vger.kernel.org
Subject: [ANNOUNCE] git tracker online
Date: Wed, 11 May 2005 07:01:18 +0000 [thread overview]
Message-ID: <1115794878.22180.27.camel@tglx> (raw)
Hi,
git tracker is online in a beta version:
http://www.tglx.de/gittracker
It does:
- multi repository tracking
- Tree browsing
- File revision history
- File diffs
- File annotation
- commit viewer with filtering (e.g. all commits in a tree which are not
in another tree)
The file histories and annotations are partially messed due to the
missing information about head forward merges. Its a pity that there
seems to be no interest to solve this problem really. It might be not
important for some of you, but it is often quite helpful to have
consistent information across multiple trees available.
The simplest solution would be a head order list per repository, which
is updated every time when the head is changed. Thats a non intrusive
feature, which could be simply added to the current tools.
tglx
next reply other threads:[~2005-05-11 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 7:01 Thomas Gleixner [this message]
2005-05-11 9:55 ` [ANNOUNCE] git tracker online Jan-Benedict Glaw
2005-05-12 19:04 ` Jan-Benedict Glaw
2005-05-12 19:58 ` Thomas Gleixner
2005-05-12 20:30 ` Jan-Benedict Glaw
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=1115794878.22180.27.camel@tglx \
--to=tglx@linutronix.de \
--cc=git@vger.kernel.org \
/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).