From: Pierre Habouzit <madcoder@debian.org>
To: Junio C Hamano <junio@pobox.com>
Cc: git@vger.kernel.org, gitster@pobox.com, joerg@debian.org
Subject: Re: [PATCH] Make git reflog expire honour core.sharedRepository.
Date: Mon, 16 Jun 2008 00:55:00 +0200 [thread overview]
Message-ID: <20080615225459.GA13472@artemis.madism.org> (raw)
In-Reply-To: <7vhcbuco2w.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
On Sun, Jun 15, 2008 at 10:47:51PM +0000, Junio C Hamano wrote:
> Pierre Habouzit <madcoder@debian.org> writes:
>
> > Signed-off-by: Pierre Habouzit <madcoder@debian.org>
> > ---
> > builtin-reflog.c | 1 +
> > t/t1301-shared-repo.sh | 15 +++++++++++++++
> > 2 files changed, 16 insertions(+), 0 deletions(-)
> >
> > Some people like to have logAllRefUpdates even for bare repositories, and if
> > shared, git-gc breaks them.
> >
> > diff --git a/builtin-reflog.c b/builtin-reflog.c
> > index 897d1dc..430929f 100644
> > --- a/builtin-reflog.c
> > +++ b/builtin-reflog.c
> > @@ -308,6 +308,7 @@ static int expire_reflog(const char *ref, const unsigned char *sha1, int unused,
> > } else if (cmd->updateref && commit_ref(lock)) {
> > status |= error("Couldn't set %s", lock->ref_name);
> > }
> > + adjust_shared_perm(log_file);
>
> Why is it sane to do this unconditionally, instead of putting in another
> else or something?
Huh indeed, the proper patch should have been:
- }
+ } else {
+ adjust_shared_perm(log_file);
+ }
It was inattention on my end, I focused more on writing a test case
than on the one liner fix. Sorry.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-15 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 21:37 [PATCH] Make git reflog expire honour core.sharedRepository Pierre Habouzit
2008-06-15 22:47 ` Junio C Hamano
2008-06-15 22:55 ` Pierre Habouzit [this message]
2008-06-16 15:15 ` Johannes Schindelin
2008-06-16 15:19 ` Johannes Schindelin
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=20080615225459.GA13472@artemis.madism.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joerg@debian.org \
--cc=junio@pobox.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