git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2020, #04; Mon, 22)
Date: Tue, 23 Jun 2020 06:00:15 -0400	[thread overview]
Message-ID: <20200623100015.GA3386564@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqimfid2l1.fsf@gitster.c.googlers.com>

On Mon, Jun 22, 2020 at 05:54:02PM -0700, Junio C Hamano wrote:

> * jk/fast-export-anonym (2020-06-22) 4 commits
>   (merged to 'next' on 2020-06-22 at b517b2f707)
>  + fast-export: allow dumping the path mapping
>  + fast-export: refactor path printing to not rely on stdout
>  + fast-export: anonymize "master" refname
>  + fast-export: allow dumping the refname mapping
> 
>  The way refnames are anonymized has been updated and a way to help
>  debugging using the anonymized output hsa been added.
> 
>  Will merge to 'master'.

This graduated much faster than I expected. I really did mean my "I'll
look at this other direction" literally. I should have something to show
later today. :)

The two techniques could complement each other, but I think the other
one might be sufficient, and seems to be coming out a little cleaner.

-Peff

  reply	other threads:[~2020-06-23 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  0:54 What's cooking in git.git (Jun 2020, #04; Mon, 22) Junio C Hamano
2020-06-23 10:00 ` Jeff King [this message]
2020-06-23 12:46 ` Johannes Schindelin
2020-06-23 19:16   ` Junio C Hamano
2020-06-28 19:22 ` `seen' datapoint [was: What's cooking in git.git (Jun 2020, #04; Mon, 22)] Eric Wong
2020-06-29  1:22   ` `seen' datapoint [ Junio C Hamano
2020-06-29  2:04     ` Eric Wong
2020-06-29 18:45       ` Jeff King
2020-06-29 19:03         ` Eric Wong

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=20200623100015.GA3386564@coredump.intra.peff.net \
    --to=peff@peff.net \
    --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).