From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Enhance core.logallrefupdates
Date: Sun, 08 Oct 2006 12:03:20 +0200 [thread overview]
Message-ID: <egaibi$bb$1@sea.gmane.org> (raw)
In-Reply-To: 7vbqonkzfe.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> This enhances core.logallrefupdates by allowing it to take
> "heads" as the value as well, which causes git to create missing
> reflog files automatically only for branch heads. Usually tags
> are create-once-and-live-forever, and it is irritating to see
> reflog files created automatically every time a new tag is made.
>
> As before, boolean "true" means create missing reflog files for
> all refs.
>
> ---
>
> * Setting it to "tags" is not supported, as it does not make
> much sense wanting to log only tag updates.
>
> Come to think of it, it might make sense to change the
> meaning of "true" to do what this patch does. I do not think
> of reasons to create missing reflog for tags automatically
> anyway.
If we change meaning of "true", perhaps (just in case in case) we
should add "all" value?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-08 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 8:02 [RFC/PATCH] Enhance core.logallrefupdates Junio C Hamano
2006-10-08 10:03 ` Jakub Narebski [this message]
2006-10-08 19:52 ` Junio C Hamano
2006-10-08 20:15 ` Jakub Narebski
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='egaibi$bb$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.