From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] nmbug: mark repository as bare on clone
Date: Sat, 12 Apr 2014 19:39:51 +0300 [thread overview]
Message-ID: <m2sipih57s.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1397320232-32458-1-git-send-email-david@tethera.net>
On Sat, Apr 12 2014, David Bremner <david@tethera.net> wrote:
> As far as I can figure out, if a git repository is non-bare, then it
> should either have core.worktree set, or the parent directory should
> be the worktree. Since the parent directory is usually the user's home
> directory, we don't want that. Although unlikely to be typed by
> mistake
Based on that info change looks reasonable. I edited my ~/.nmbug/config
and changed bare = false -> bare = true and nothing borke so far.
so +1 from me.
Tomi
>
> % cd $HOME && ln -s .nmbug .git && git reset --hard
>
> would delete a bunch of files.
> ---
>
> Hah, I managed to escalate a documentation quibble into a
> sortof-security issue.
>
> devel/nmbug/nmbug | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/devel/nmbug/nmbug b/devel/nmbug/nmbug
> index d6f5213..b18ded7 100755
> --- a/devel/nmbug/nmbug
> +++ b/devel/nmbug/nmbug
> @@ -134,6 +134,7 @@ sub do_clone {
> $repository, $tempwork) == 0
> or die "'git clone' exited with nonzero value\n";
> git ('config', '--unset', 'core.worktree');
> + git ('config', 'core.bare', 'true');
> }
>
> sub is_committed {
> --
> 1.9.1
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2014-04-12 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 16:30 [PATCH] nmbug: mark repository as bare on clone David Bremner
2014-04-12 16:39 ` Tomi Ollila [this message]
2014-04-12 17:09 ` David Bremner
2014-04-15 17:23 ` W. Trevor King
2014-04-15 20:33 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2sipih57s.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).