From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: whitespace cleanup around '='
Date: Thu, 22 Jun 2006 09:32:09 +0200 [thread overview]
Message-ID: <e7dh1c$61n$1@sea.gmane.org> (raw)
In-Reply-To: 7vejxhwts4.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> @@ -326,7 +326,7 @@ EOF
>> } elsif (defined $hash) {
>> $search_hash = $hash;
>> } else {
>> - $search_hash = "HEAD";
>> + $search_hash = "HEAD";
>> }
>> $cgi->param("a", "search");
>> $cgi->param("h", $search_hash);
>
> My copy from "next" has this part like the following:
>
> if (!defined $searchtext) {
> $searchtext = "";
> }
> my $search_hash;
> if (defined $hash) {
> $search_hash = $hash;
> } else {
> $search_hash = "HEAD";
> }
>
> I thought we were both reasonably sure that we are now in
> sync... I could apply it by hand but once I start doing that
> I'm afraid we will never converge.
>
> It's quite frustrating.
I'm very sorry, I forgot that I applied Timo Hirvonen patch
"[PATCH] gitweb: Start search from HEAD"
(<20060620152515.23e59396.tihirvon@gmail.com>)
http://permalink.gmane.org/gmane.comp.version-control.git/22197>
on top of 'next'.
This patch fixes search quite nicely, reducing significantly number of error
messages during search (e.g. starting search from blob or file view).
Any reason not to apply it?
>> my $path = esc_html(chop_str($proj{'path'}, 25, 5));
>> - my $rss = "$my_url?p=$proj{'path'};a=rss";
>> - my $html = "$my_url?p=$proj{'path'};a=summary";
>> + my $rss = "$my_url?p=$proj{'path'};a=rss";
>> + my $html = "$my_url?p=$proj{'path'};a=summary";
>
> Are you sure you want to do "my $rss two-spaces equal space"?
>
> I've fixed up the whitespace you missed and will be applying the
> following on top of what is in "next" tonight.
>
> -- >8 --
> gitweb: do not align assignment = with extra whitespaces
My idea for coding style is to align assignment = with extra whitespaces,
but only where aligned assignments statements are one after another.
The above "my $rss" example was mistyped as " = " instead of " = ",
but I think it was meant to be aligned at '='. IMHO aligning at assign
makes code more readable.
But that is just my opinion.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-06-22 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 12:42 gitk lower pane (commit and files view) scrollbar extends past gitk window Jakub Narebski
2006-06-22 0:35 ` Edgar Toernig
2006-06-22 6:52 ` [PATCH] gitweb: whitespace cleanup around '=' Jakub Narebski
2006-06-22 7:01 ` Jakub Narebski
2006-06-22 7:09 ` Junio C Hamano
2006-06-22 7:32 ` Jakub Narebski [this message]
2006-06-22 9:33 ` Junio C Hamano
2006-06-22 9:37 ` Jakub Narebski
2006-06-22 10:20 ` Junio C Hamano
2006-06-22 9:52 ` Jakub Narebski
2006-06-22 10:19 ` Santi Béjar
2006-06-22 7:10 ` gitk lower pane (commit and files view) scrollbar extends past gitk window Alex Riesen
2006-06-22 7:48 ` [WORKAROUND] gitk lower pane " Jakub Narebski
2006-06-22 13:19 ` Jakub Narebski
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='e7dh1c$61n$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).