From: john at keeping.me.uk (John Keeping)
Subject: [PATCH] Regression fix: Make section-from-path=-1 work again
Date: Tue, 16 Apr 2013 18:39:58 +0100 [thread overview]
Message-ID: <20130416173958.GN2278@serenity.lan> (raw)
In-Reply-To: <20130416145032.GB97089@plenz.com>
From 1e4ddf8174341e6caa281d007a7e269183b9aca8 Mon Sep 17 00:00:00 2001
Message-Id: <1e4ddf8174341e6caa281d007a7e269183b9aca8.1366133788.git.john at keeping.me.uk>
From: John Keeping <john at keeping.me.uk>
Date: Tue, 16 Apr 2013 18:33:25 +0100
Subject: [PATCH] scan-tree: fix "section-from-path = -N"
Commit fb3655d (use struct strbuf instead of static buffers -
2013-04-06) introduced a regression in the "section-from-path" handling
when the configured value is negative. By changing the "rel" variable
so that it includes a trailing slash, counting slashes from the end of
the string no longer gives the same answer as it did before.
Fix this by ensuring that "rel" does not have a trailing slash.
Reported-by: Julius Plenz <plenz at cis.fu-berlin.de>
Signed-off-by: John Keeping <john at keeping.me.uk>
---
On Tue, Apr 16, 2013 at 04:50:32PM +0200, Julius Plenz wrote:
> * John Keeping <john at keeping.me.uk> [2013-04-16 16:30]:
> > This is the "rel" buffer, not "path" so I think it would be better
> > to just strip any trailing slash from "rel" when it is assigned.
> > This has the benefit of also making sure we don't have a trailing
> > '/' in the section name.
>
> Sure, that sounds better. I didn't really spend much time with your
> new code. If you supply a patch I'll try it in my installation.
I was hoping you might want to re-roll your patch taking that
approach... ;-)
It would be nice to have a test covering this, but to do it well I think
we should built a bit more CGit-specific test infrastructure, which is
more work that I want to do at the moment.
scan-tree.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scan-tree.c b/scan-tree.c
index beb584b..a1ec8fb 100644
--- a/scan-tree.c
+++ b/scan-tree.c
@@ -113,6 +113,8 @@ static void add_repo(const char *base, struct strbuf *path, repo_config_fn fn)
if (!strcmp(rel.buf + rel.len - 5, "/.git"))
strbuf_setlen(&rel, rel.len - 5);
+ else if (rel.len && rel.buf[rel.len - 1] == '/')
+ strbuf_setlen(&rel, rel.len - 1);
repo = cgit_add_repo(rel.buf);
config_fn = fn;
--
1.8.2.694.ga76e9c3.dirty
next prev parent reply other threads:[~2013-04-16 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 14:10 plenz
2013-04-16 14:30 ` john
2013-04-16 14:50 ` plenz
2013-04-16 17:39 ` john [this message]
2013-04-17 11:38 ` plenz
2013-04-17 11:41 ` 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=20130416173958.GN2278@serenity.lan \
--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).