From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] gitweb: Great subroutines renaming
Date: Wed, 09 Aug 2006 04:11:02 -0700 [thread overview]
Message-ID: <7vpsfa4115.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <ebcf9s$h32$1@sea.gmane.org> (Jakub Narebski's message of "Wed, 09 Aug 2006 13:01:32 +0200")
Jakub Narebski <jnareb@gmail.com> writes:
> It's not a problem to do '...'/'next' link _after_ the body, but
> the paging navigation bar is at the _top_ of page, before
> outputting the body.
A good web engineering practice is to prepare the data before
you generate a single line of output, so after or top should not
make a difference, I would think.
next prev parent reply other threads:[~2006-08-09 11:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 14:26 [PATCH/RFC] gitweb: Great subroutines renaming Jakub Narebski
2006-08-07 19:37 ` Junio C Hamano
2006-08-07 21:47 ` Jakub Narebski
2006-08-07 21:52 ` Jakub Narebski
2006-08-07 22:00 ` Junio C Hamano
2006-08-07 22:15 ` Jakub Narebski
2006-08-07 22:58 ` Jakub Narebski
2006-08-07 23:49 ` Junio C Hamano
2006-08-08 0:10 ` Jakub Narebski
2006-08-08 9:38 ` Jakub Narebski
2006-08-08 20:18 ` Junio C Hamano
2006-08-08 20:24 ` Jakub Narebski
2006-08-08 9:51 ` Jakub Narebski
2006-08-08 18:12 ` git-show-refs (was: [PATCH/RFC] gitweb: Great subroutines renaming) Jakub Narebski
2006-08-09 10:26 ` [PATCH/RFC] gitweb: Great subroutines renaming Jakub Narebski
2006-08-09 10:51 ` Junio C Hamano
2006-08-09 11:01 ` Jakub Narebski
2006-08-09 11:11 ` Junio C Hamano [this message]
2006-08-08 9:48 ` Jakub Narebski
2006-08-08 21:13 ` Jakub Narebski
2006-08-08 21:50 ` Junio C Hamano
2006-08-08 22:33 ` Jakub Narebski
2006-08-09 20:54 ` Jakub Narebski
2006-08-09 21:11 ` Junio C Hamano
2006-08-10 7:57 ` Jakub Narebski
2006-08-12 23:09 ` Jakub Narebski
2006-08-13 2:21 ` Junio C Hamano
2006-08-13 2:27 ` Junio C Hamano
2006-08-13 9:29 ` Jakub Narebski
2006-08-14 0:11 ` 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=7vpsfa4115.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.