From: Erick Mattos <erick.mattos@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/5] refs: split log_ref_write logic into log_ref_setup
Date: Wed, 2 Jun 2010 20:16:30 -0300 [thread overview]
Message-ID: <AANLkTikcQny9Es_cMJTg94qTJZD2s7T37h_Hur9Lt-Lv@mail.gmail.com> (raw)
In-Reply-To: <7vzkzdcneh.fsf@alter.siamese.dyndns.org>
Hi,
2010/6/2 Junio C Hamano <gitster@pobox.com>:
> Erick Mattos <erick.mattos@gmail.com> writes:
>
>> Now just a question, Junio:
>>
>> I forgot to sign-off those patches, should I have to send them again?
>
> I would have appreciated a whole re-send while I was too distracted by
> non-git stuff during the past few weeks, but now I am more or less settled
> in, it's Ok to just send a separate "Signed-off-by:" like this one:
>
> http://article.gmane.org/gmane.comp.version-control.git/148230/raw
>
All right, following then:
2010/5/21 Erick Mattos <erick.mattos@gmail.com>:
> These series of patches are improvements to 'git checkout --orphan'.
>
> The main reason for them is a corner case which is not being solved by
> actual implementation. As it is a quite improbable situation and as it was
> necessary to do more extensive changes to support it then its development
> was held to be presented in a new developing cycle.
>
> When someone set core.logAllRefUpdates to false reflogs are not created
> automatically. This behavior is superseeded by -l option. Actually this is
> not allowed with --orphan by current implementation. Those new patches are
> made to fix that.
>
> There are also two other patches for configuring completion in bash and to
> enhance documentation.
>
> To be completely honest I don't see a point of not having the reflogs
> created and deleted automatically so I see no reason for -l and
> core.logAllRefUpdates at all. But I do not like to do anything partially
> thus these new patches. If someone could show me a case please do it. ;-)
>
> [PATCH 1/5] Documentation: alter checkout --orphan description
>
> This one improves documentation text by late corrections from previous
> threads.
>
> [PATCH 2/5] refs: split log_ref_write logic into log_ref_setup
>
> Prepare the field by separating the logic to set up the reflog from the
> reflog writing action.
>
> [PATCH 3/5] checkout --orphan: respect -l option always
>
> This is the actual actor.
>
> [PATCH 4/5] t3200: test -l with core.logAllRefUpdates options
>
> Adjusting scripts to test everything extensively.
>
> [PATCH 5/5] bash completion: add --orphan to 'git checkout'
>
> Just do that git change.
Signed-off-by: Erick Mattos <erick.mattos@gmail.com>
next prev parent reply other threads:[~2010-06-02 23:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 0:28 [PATCH 0/5] checkout --orphan improvements Erick Mattos
2010-05-22 0:28 ` [PATCH 1/5] Documentation: alter checkout --orphan description Erick Mattos
2010-05-22 0:28 ` [PATCH 2/5] refs: split log_ref_write logic into log_ref_setup Erick Mattos
2010-05-26 5:07 ` Junio C Hamano
2010-05-26 18:11 ` Erick Mattos
2010-06-02 18:14 ` Junio C Hamano
2010-06-02 23:16 ` Erick Mattos [this message]
2010-05-22 0:28 ` [PATCH 3/5] checkout --orphan: respect -l option always Erick Mattos
2010-05-26 5:07 ` Junio C Hamano
2010-05-26 14:52 ` Erick Mattos
2010-05-26 15:13 ` Erik Faye-Lund
2010-05-26 16:01 ` Erick Mattos
2010-06-03 16:28 ` Erick Mattos
2010-05-26 15:31 ` Michael J Gruber
2010-05-26 18:04 ` Erick Mattos
2010-05-27 7:50 ` Michael J Gruber
2010-05-22 0:28 ` [PATCH 4/5] t3200: test -l with core.logAllRefUpdates options Erick Mattos
2010-05-22 0:43 ` [PATCH 5/5] bash completion: add --orphan to 'git checkout' Erick Mattos
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=AANLkTikcQny9Es_cMJTg94qTJZD2s7T37h_Hur9Lt-Lv@mail.gmail.com \
--to=erick.mattos@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@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;
as well as URLs for NNTP newsgroup(s).