From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Marking abandoned branches
Date: Wed, 13 Sep 2006 21:34:24 +0200 [thread overview]
Message-ID: <ee9mff$qd1$1@sea.gmane.org> (raw)
In-Reply-To: 7vbqpja8wz.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> By the way, does gitweb still walk $GIT_DIR/refs hierarchy by
> hand to find out the set of refs? When Linus is done with his
> refs/ work, that way would become unsupported. You would need
> to read from "ls-remote $GIT_DIR".
Still, unfortunately. We could change git_get_references to use
'git ls-remotes $GIT_DIR' (or 'git --git-dir=$GIT_DIR ls-remotes .'),
and use git_get_references("refs/heads") in git_heads (and git_summary),
and git_get_references("refs/tags") in git_tags. This _could_ be slower
than current implementation. git-show-refs would help a bit, but I'd rather
have git-show-refs in released version of git before using it in gitweb.
Moreover, git currently reads appropriate ref directly in
git_get_hash_by_ref, not supporting even symrefs, not to mention packed
refs. One solution would be to add support for symrefs and packed refs
directly in gitweb (Git.pm can help here), another to use git core command
(git-rev-parse?) but that can make gitweb slower (additional fork).
I hope that Linus work will be left to mature first in 'pu', then in 'next'
branch... wouldn't refs cache (similar to current index for files) be
better idea?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-13 19:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 15:17 Marking abandoned branches Jon Smirl
2006-09-13 15:24 ` Petr Baudis
2006-09-13 15:31 ` Johannes Schindelin
2006-09-13 15:45 ` Jakub Narebski
2006-09-13 18:40 ` Junio C Hamano
2006-09-13 18:51 ` Jakub Narebski
2006-09-13 19:00 ` Junio C Hamano
2006-09-13 19:34 ` Jakub Narebski [this message]
2006-09-13 20:43 ` Petr Baudis
2006-09-13 20:45 ` Junio C Hamano
2006-09-13 21:02 ` Jakub Narebski
2006-09-13 21:09 ` Jakub Narebski
2006-09-13 21:32 ` Jakub Narebski
2006-09-13 15:59 ` Jon Smirl
2006-09-13 16:05 ` Johannes Schindelin
2006-09-13 17:22 ` Jon Smirl
2006-09-13 17:32 ` Shawn Pearce
2006-09-13 17:46 ` Nicolas Pitre
2006-09-13 20:31 ` Martin Langhoff
2006-09-13 20:43 ` Jakub Narebski
2006-09-13 16:09 ` Shawn Pearce
2006-09-13 16:12 ` Jakub Narebski
2006-09-13 16:40 ` A Large Angry SCM
2006-09-13 16:49 ` Shawn Pearce
2006-09-13 18:58 ` Junio C Hamano
2006-09-13 16:55 ` Jakub Narebski
2006-09-13 17:24 ` Jon Smirl
2006-09-13 17:45 ` Jakub Narebski
2006-09-14 3:37 ` Sam Vilain
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='ee9mff$qd1$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).