From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/* topics (was: Re: What's cooking in git.git (Nov 2018, #01; Thu, 1))
Date: Thu, 01 Nov 2018 12:02:01 +0100 [thread overview]
Message-ID: <8736slkqmu.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqd0rpt8wy.fsf@gitster-ct.c.googlers.com>
On Thu, Nov 01 2018, Junio C Hamano wrote:
> * ab/push-dwim-dst (2018-10-29) 9 commits
> - SQUASH???
> - push doc: document the DWYM behavior pushing to unqualified <dst>
> - push: add DWYM support for "git push refs/remotes/...:<dst>"
> - push: test that <src> doesn't DWYM if <dst> is unqualified
> - push: add an advice on unqualified <dst> push
> - push: move unqualified refname error into a function
> - push: improve the error shown on unqualified <dst> push
> - i18n: remote.c: mark error(...) messages for translation
> - remote.c: add braces in anticipation of a follow-up change
>
> "git push $there $src:$dst" rejects when $dst is not a fully
> qualified refname and not clear what the end user meant. The
> codepath has been taught to give a clearer error message, and also
> guess where the push should go by taking the type of the pushed
> object into account (e.g. a tag object would want to go under
> refs/tags/).
>
> The last few steps are questionable.
> cf. <87in1lkw54.fsf@evledraar.gmail.com>
Will send an update to this soon.
> * ab/pack-tests-cleanup (2018-10-31) 3 commits
> - index-pack tests: don't leave test repo dirty at end
> - pack-objects tests: don't leave test .git corrupt at end
> - pack-objects test: modernize style
>
> A couple of tests used to leave the repository in a state that is
> deliberately corrupt, which have been corrected.
>
> Will merge to 'next'.
Thanks!
> * ab/reject-alias-loop (2018-10-19) 1 commit
> (merged to 'next' on 2018-10-26 at bc213f1bef)
> + alias: detect loops in mixed execution mode
>
> Two (or more) aliases that mutually refer to each other can form an
> infinite loop; we now attempt to notice and stop.
>
> Discarded.
> Reverted out of 'next'.
> cf. <87sh0slvxm.fsf@evledraar.gmail.com>
*nod* will try to find time to work on this soon, but treating it as
non-urgent.
Could you please pick up
https://public-inbox.org/git/20181024114725.3927-1-avarab@gmail.com/ ?
It seems to have fallen between the cracks and addressed the feedback on
v1, and looks good to me (and nobody's objected so far...).
next prev parent reply other threads:[~2018-11-01 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 9:59 What's cooking in git.git (Nov 2018, #01; Thu, 1) Junio C Hamano
2018-11-01 11:02 ` Ævar Arnfjörð Bjarmason [this message]
2018-11-01 13:10 ` ab/* topics (was: Re: What's cooking in git.git (Nov 2018, #01; Thu, 1)) SZEDER Gábor
2018-11-01 13:46 ` Ævar Arnfjörð Bjarmason
2018-11-01 14:30 ` SZEDER Gábor
2018-11-01 13:28 ` ab/* topics Junio C Hamano
2018-11-01 15:32 ` Duy Nguyen
2018-11-01 19:38 ` Ævar Arnfjörð Bjarmason
2018-11-01 16:07 ` master updated? (was Re: What's cooking in git.git (Nov 2018, #01; Thu, 1)) Derrick Stolee
2018-11-02 0:04 ` Junio C Hamano
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=8736slkqmu.fsf@evledraar.gmail.com \
--to=avarab@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).