From: Jonathan Nieder <jrnieder@gmail.com>
To: Anders Kaseorg <andersk@MIT.EDU>
Cc: julio.lajara@alum.rpi.edu, git@vger.kernel.org,
Jakub Narebski <jnareb@gmail.com>,
Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Subject: Re: Potential bug in gitweb 1.7.2
Date: Mon, 26 Jul 2010 10:23:56 -0500 [thread overview]
Message-ID: <20100726152356.GA6564@burratino> (raw)
In-Reply-To: <alpine.DEB.2.00.1007260508290.14251@dr-wily.mit.edu>
Hi Anders,
Anders Kaseorg wrote:
> the 1.7.2-0ppa1 package in the git-core PPA
> was constructed by merging your jrn/for-gerrit branch (1.7.2~rc3-0.1,
> commit f84e1eb) with upstream v1.7.2, and updating
> debian/versions.upstream and debian/changelog.upstream. It already
> includes that commit.
Good to know. Is there a public git repository for the PPA? (I am
asking selfishly, because it would be convenient to be able to tell
what commit each version corresponds to and to steal changes
back.)
> Indeed, when I install the gitweb 1.7.2-0ppa1 package, put some
> repositories into /var/cache/git, and go to http://localhost/gitweb/ , it
> works correctly for me.
Hm, I should have tried that myself.
Thanks.
next prev parent reply other threads:[~2010-07-26 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 4:55 Potential bug in gitweb 1.7.2 Julio Lajara
2010-07-26 5:08 ` Jonathan Nieder
2010-07-26 9:27 ` Anders Kaseorg
2010-07-26 13:10 ` Julio Lajara
2010-07-26 13:36 ` Jakub Narebski
2010-07-26 13:39 ` Ævar Arnfjörð Bjarmason
2010-07-26 13:52 ` Julio Lajara
2010-07-26 14:23 ` Jakub Narebski
2010-07-31 3:01 ` [PATCH/RFC] gitweb: allow configurations that change with each request Jonathan Nieder
2010-08-02 19:35 ` Jakub Narebski
2010-08-02 21:01 ` Jonathan Nieder
2010-08-02 21:25 ` Jakub Narebski
2010-07-26 15:23 ` Jonathan Nieder [this message]
2010-07-26 18:50 ` Potential bug in gitweb 1.7.2 Anders Kaseorg
2010-07-27 0:09 ` Jonathan Nieder
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=20100726152356.GA6564@burratino \
--to=jrnieder@gmail.com \
--cc=andersk@MIT.EDU \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=julio.lajara@alum.rpi.edu \
--cc=pavan.sss1991@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).