From: Jakub Narebski <jnareb@gmail.com>
To: "Tjernlund" <tjernlund@tjernlund.se>
Cc: "'git'" <git@vger.kernel.org>
Subject: Re: gitweb improvements
Date: Sun, 05 Oct 2008 10:22:18 -0700 (PDT) [thread overview]
Message-ID: <m34p3rq7og.fsf@localhost.localdomain> (raw)
In-Reply-To: <00a201c92701$54ec6980$fec53c80$@se>
"Tjernlund" <tjernlund@tjernlund.se> writes:
> When I browse a repo using gitweb, I miss two things:
> 1) looking at the history for a file or directory I really want
> to see the tags there too.
Should be easy to do, but would probably wait (and be indirect result)
of refactoring/unification of log-like views code ('log', 'shortlog',
'history', perhaps also 'rss', 'atom', 'search')
I have added it to my gitweb TODO list...
> 2) looking at a merge like:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=66120005e65eed8a05b14a36ab448bdec42f0d6b
> is somewhat confusing. It really doesn't tell you which commits that is
> included in the merge.
I don't understand you there. First, you have "(merge: 0d0f3ef 9778e9a)"
in the navbar, so you can easily go to commit view for parents. Second,
among commit headers you have two "parent", where SHA-1 of a commit is
hidden link, and there are also 'commit' and 'diff' link for those.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-10-05 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 15:45 gitweb improvements Tjernlund
2008-10-05 17:22 ` Jakub Narebski [this message]
2008-10-05 22:25 ` Tjernlund
2008-10-05 23:54 ` Jakub Narebski
2008-10-06 22:17 ` Tjernlund
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=m34p3rq7og.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=tjernlund@tjernlund.se \
/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).