From: Tobias.Bieniek at gmx.de (Tobias Bieniek)
Subject: [PATCH 1/3] Added "sort-sections" flag for the repository listing
Date: Wed, 10 Oct 2012 00:26:39 +0200 [thread overview]
Message-ID: <CABEOeT=qL4nCvPz0Q+sHVr2CDDoRHh42mm5XfLXBQdSJMTU7jA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rx1g-28M-sL6jUMqK3VkX7pvGQk+eWmTeVB9jpVERWtw@mail.gmail.com>
2012/10/10 Jason A. Donenfeld <Jason at zx2c4.com>:
> On Tue, Oct 9, 2012 at 11:49 PM, Tobias Bieniek <Tobias.Bieniek at gmx.de> wrote:
>>
>> We have used the strict date ordering at http://git.xcsoar.org/ for a
>> few months now and we did not experience any issues at all.
>
> It doesn't look like commit graph is enabled there?
>
> I'll need to spend some time looking through this to be sure commit
> graph doesn't explode -- it's fairly sensitive.
it is enabled. see http://git.xcsoar.org/cgit/master/xcsoar.git/log/
for example.
whether it is exploding or not depends on the repo, I guess. but I
would let the users decide whether they want the date-ordering or not.
the default should obviously be similar to the default of the git log
command.
next prev parent reply other threads:[~2012-10-09 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 15:38 Tobias.Bieniek
2012-07-02 15:38 ` [PATCH 2/3] Added "date-order" and "topo-order" flags Tobias.Bieniek
2012-07-02 15:38 ` [PATCH 3/3] Fixed parameter parsing in repo_config() function Tobias.Bieniek
[not found] ` <CABEOeT=yfWaqRfanCcgVYLkTa3PD8JtkfvY2NfTGxNOAO2PEFQ@mail.gmail.com>
2012-10-08 21:11 ` [PATCH 1/3] Added "sort-sections" flag for the repository listing Jason
2012-10-09 18:59 ` Tobias.Bieniek
2012-10-09 19:03 ` Jason
2012-10-09 19:10 ` Jason
2012-10-09 19:11 ` Jason
2012-10-09 21:54 ` Tobias.Bieniek
2012-10-09 22:16 ` Jason
2012-10-09 21:49 ` Tobias.Bieniek
2012-10-09 22:15 ` Jason
2012-10-09 22:26 ` Tobias.Bieniek [this message]
2012-10-13 14:24 ` Tobias.Bieniek
2012-10-09 21:47 ` Tobias.Bieniek
2012-10-09 19:12 ` Jason
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='CABEOeT=qL4nCvPz0Q+sHVr2CDDoRHh42mm5XfLXBQdSJMTU7jA@mail.gmail.com' \
--to=cgit@lists.zx2c4.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).