git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kacper Kornet <draenog@pld-linux.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitweb: Option to not display information about owner
Date: Thu, 26 Apr 2012 18:35:02 +0200	[thread overview]
Message-ID: <20120426163502.GH16489@camk.edu.pl> (raw)
In-Reply-To: <xmqqaa1ya3rh.fsf@junio.mtv.corp.google.com>

On Thu, Apr 26, 2012 at 08:53:22AM -0700, Junio C Hamano wrote:
> Kacper Kornet <draenog@pld-linux.org> writes:

> >> I am guessing both #5401 and #5551 are $it->{'category'} of @projects[]
> >> elements.

> > Yes, I have tested the tree with:

> > gitweb: Improve repository verification
> > gitweb: Option to omit column with time of the last change
> > gitweb: Option to not display information about owner

> > applied on top of v1.7.10. And all tests except 't91??' are passed.
> > Could you write on top of which revision have you applied these three
> > patches?

> Let's see...

> $ git log --oneline --first-parent --boundary master..kk/gitweb-omit-expensive
> 37e2621 gitweb: Option to not display information about owner
> 5710be4 gitweb: Option to omit column with time of the last change
> 75e0dff gitweb: Don't set owner if got empty value from projects.list
> - fdec2eb Merge branch 'maint-1.7.9' into maint

> I replayed these three on v1.7.10^0

> $ git checkout v1.7.10^0
> $ git format-patch --stdout fdec2eb..kk/gitweb-omit-expensive | git am -s3c

> and the result fails exactly the same way, though.

Appereantly I have managed to send the different patch then I have
applied in my private tree. I'm sorry for my mistake. In a short time I
will send the correct one.

-- 
  Kacper Kornet

  reply	other threads:[~2012-04-26 16:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 13:27 [PATCH] gitweb: Option to omit column with time of the last change Kacper Kornet
2012-04-03 23:12 ` Jakub Narebski
2012-04-04  6:39   ` Kacper Kornet
2012-04-04 14:31     ` Jakub Narebski
2012-04-04 16:22       ` Kacper Kornet
2012-04-14 13:16         ` Jakub Narebski
2012-04-16 10:12           ` Kacper Kornet
2012-04-16 20:06             ` Jakub Narebski
2012-04-16 21:39               ` Kacper Kornet
2012-04-17 23:36                 ` Jakub Narebski
2012-04-19 16:07                   ` [PATCH] gitweb: Improve repository verification Jakub Narebski
2012-04-19 18:30                     ` Junio C Hamano
2012-04-19 19:46                       ` Jakub Narebski
2012-04-21 11:28                         ` Jakub Narebski
2012-04-24 17:39                     ` [PATCH 1/2] gitweb: Option to omit column with time of the last change Kacper Kornet
2012-04-24 17:41                     ` [PATCH 2/2] gitweb: Option to not display information about owner Kacper Kornet
2012-04-26  4:39                       ` Junio C Hamano
2012-04-26 15:07                         ` Kacper Kornet
2012-04-26 15:53                           ` Junio C Hamano
2012-04-26 16:35                             ` Kacper Kornet [this message]
2012-04-26 16:45                               ` [PATCH v2 " Kacper Kornet
2012-04-24 17:36                   ` [PATCH] gitweb: Option to omit column with time of the last change Kacper Kornet
2012-04-04 17:14       ` 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=20120426163502.GH16489@camk.edu.pl \
    --to=draenog@pld-linux.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 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).