git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #02; Fri, 8)
Date: Sat, 09 Jan 2021 11:55:15 +0100	[thread overview]
Message-ID: <871reu752k.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqk0sni68g.fsf@gitster.c.googlers.com>


On Fri, Jan 08 2021, Junio C Hamano wrote:

> 	git://git.kernel.org/pub/scm/git/git.git/
> 	git://repo.or.cz/alt-git.git/
> 	https://kernel.googlesource.com/pub/scm/git/git/
> 	https://github.com/git/git/
> 	https://gitlab.com/git-vcs/git/

As an aside thanks for following-up on adding the git-vcs/git URL. I
don't think I responded to a question in that E-Mail chain about whether
this repo only has your branches (and not some random topic branches of
mine or whatever). That's the case, it's a strict mirror of your
push-outs.

> * ab/trailers-extra-format (2020-12-09) 5 commits
>   (merged to 'next' on 2020-12-14 at 9fc731944e)
>  + pretty format %(trailers): add a "key_value_separator"
>  + pretty format %(trailers): add a "keyonly"
>  + pretty-format %(trailers): fix broken standalone "valueonly"
>  + pretty format %(trailers) doc: avoid repetition
>  + pretty format %(trailers) test: split a long line
>
>  The "--format=%(trailers)" mechanism gets enhanced to make it
>  easier to design output for machine consumption.

Thanks! Am refactoring some out-of-tree code to take advantage of this
:)

I forgot that, oops. Is just declaring here that all of that's:

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>

Since you have some acks etc. squashed into it at this point...

> * bc/hashed-mailmap (2020-12-12) 1 commit
>  - mailmap: support hashed entries in mailmaps
>
>  The mailmap database learned to take hashed value as the original
>  side of mapping.
>
>  Expecting a reroll.

FWIW there was since a re-roll on 2021-01-03, but the discussion is
sort-of outstanding, so maybe that's intentional...

> * ab/mktag (2021-01-06) 23 commits
>   (merged to 'next' on 2021-01-08 at 6f9e11ad97)
>  + mktag: add a --[no-]strict option
>  + mktag: mark strings for translation
>  + mktag: convert to parse-options
>  + mktag: allow omitting the header/body \n separator
>  + mktag: allow turning off fsck.extraHeaderEntry
>  + fsck: make fsck_config() re-usable
>  + mktag: use fsck instead of custom verify_tag()
>  + mktag: use puts(str) instead of printf("%s\n", str)
>  + mktag: remove redundant braces in one-line body "if"
>  + mktag: use default strbuf_read() hint
>  + mktag tests: test verify_object() with replaced objects
>  + mktag tests: improve verify_object() test coverage
>  + mktag tests: test "hash-object" compatibility
>  + mktag tests: stress test whitespace handling
>  + mktag tests: run "fsck" after creating "mytag"
>  + mktag tests: don't create "mytag" twice
>  + mktag tests: don't redirect stderr to a file needlessly
>  + mktag tests: remove needless SHA-1 hardcoding
>  + mktag tests: use "test_commit" helper
>  + mktag tests: don't needlessly use a subshell
>  + mktag doc: update to explain why to use this
>  + mktag doc: grammar fix, when exists -> when it exists
>  + mktag doc: say <hash> not <sha1>
>
>  "git mktag" validates its input using its own rules before writing
>  a tag object---it has been updated to share the logic with "git
>  fsck".
>
>  Will merge to 'master'.

Thanks. I've got some more local fsck-y fixes I'm hoping to submit soon.

  reply	other threads:[~2021-01-09 10:57 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 19:22 What's cooking in git.git (Jan 2021, #02; Fri, 8) Junio C Hamano
2021-01-09 10:55 ` Ævar Arnfjörð Bjarmason [this message]
2021-01-09 21:28   ` Junio C Hamano
2021-01-09 22:05     ` brian m. carlson
2021-01-09 23:20       ` Junio C Hamano
2021-01-11  1:53         ` brian m. carlson
2021-01-11 19:04           ` Junio C Hamano
2021-01-12 14:00             ` Ævar Arnfjörð Bjarmason
2021-01-14 23:52               ` Emily Shaffer
2021-01-14 23:56                 ` Emily Shaffer
2021-01-15  7:22                   ` Junio C Hamano
2021-01-15  0:29                 ` brian m. carlson
2021-01-15  1:44                 ` Junio C Hamano
2021-01-16 16:23                 ` Ævar Arnfjörð Bjarmason
2021-01-17 17:15                   ` Jeff King
2021-01-17 20:22                     ` Ævar Arnfjörð Bjarmason
2021-01-10 19:00     ` Ævar Arnfjörð Bjarmason
2021-01-11  0:21       ` Junio C Hamano
2021-01-09 21:38 ` David Aguilar
2021-01-09 23:08   ` Junio C Hamano
2021-01-14 23:06 ` Emily Shaffer
2021-01-15  1:50   ` Junio C Hamano
2021-01-15  2:24     ` Taylor Blau
2021-01-15  2:44       ` Taylor Blau
2021-01-15  2:36   ` Derrick Stolee
2021-01-15  2:54     ` Derrick Stolee
2021-01-15  6:36     ` Junio C Hamano
2021-01-15  6:38       ` Junio C Hamano
2021-01-15 11:36         ` Derrick Stolee
2021-01-15 19:44           ` Junio C Hamano
2021-01-15 20:08             ` Emily Shaffer
2021-01-15 20:59               ` Junio C Hamano
2021-01-15 19:52 ` Jeff King
2021-01-15 21:40   ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871reu752k.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.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).