From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Enhance core.logallrefupdates
Date: Sun, 08 Oct 2006 22:15:06 +0200 [thread overview]
Message-ID: <egbm6h$7mu$1@sea.gmane.org> (raw)
In-Reply-To: 7vr6xiio02.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>>> 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?
>
> Didn't I just say that I do not think of reasons to do so ;-)?
>
> Saying "just in case" is not enough. You need to say at least
> "this hypothetical workflow which requires to update refs/xxx
> and doing automated reflog creation only under refs/heads makes
> that workflow less convenient".
If I remember correctly there was example of workflow which did
fetch remote heads to local tags. But I'm not sure if this reflog
made sense with that workflow.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-10-08 20:15 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
2006-10-08 19:52 ` Junio C Hamano
2006-10-08 20:15 ` Jakub Narebski [this message]
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='egbm6h$7mu$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 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).