From: Eric Sunshine <sunshine@sunshineco.com> To: Junio C Hamano <gitster@pobox.com> Cc: Git List <git@vger.kernel.org> Subject: Re: What's cooking in git.git (Sep 2020, #03; Wed, 9) Date: Wed, 9 Sep 2020 19:07:22 -0400 Message-ID: <CAPig+cQnnukVoJTgsu1sGFWkAYv7V38-0s-CgYuMyizYHhSFQQ@mail.gmail.com> (raw) In-Reply-To: <xmqq4ko6twc9.fsf@gitster.c.googlers.com> On Wed, Sep 9, 2020 at 6:33 PM Junio C Hamano <gitster@pobox.com> wrote: > * es/format-patch-interdiff-cleanup (2020-09-08) 3 commits > - format-patch: use 'origin' as start of current-series-range when known > - diff-lib: tighten show_interdiff()'s interface > - diff: move show_interdiff() from its own file to diff-lib > > Code cleanup with a slight behaviour change when "format-patch > --range-diff=<prev> origin..HEAD" gives a single revision to > <prev>. Perhaps this could be a bit more precise by saying something like: Code cleanup and make "format-patch --range-diff=<prev> <origin>..HEAD" not ignore <origin> when <prev> is a single revision. > * es/wt-add-detach (2020-09-06) 3 commits > - git-worktree.txt: discuss branch-based vs. throwaway worktrees > - worktree: teach `add` to recognize -d as shorthand for --detach > - git-checkout.txt: document -d short option for --detach > > "git worktree add" learns the "--detach" option to create a new > worktree without being on a branch. This needs a tweak to avoid being incorrect. "git worktree add" has understood --detach from the start. This series only teaches it -d as an alias for --detach. So, perhaps: "git worktree add" learns "-d" as short for "--detach".
next prev parent reply index Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-09 22:32 Junio C Hamano 2020-09-09 23:07 ` Eric Sunshine [this message] 2020-09-10 4:52 ` Junio C Hamano 2020-09-15 22:48 ` Eric Sunshine 2020-09-15 22:54 ` Junio C Hamano 2020-09-15 19:05 ` Jakub Narębski 2020-09-15 19:32 ` Taylor Blau 2020-09-15 21:14 ` Junio C Hamano 2020-09-15 21:25 ` Jakub Narębski 2020-09-15 21:45 ` Junio C Hamano 2020-09-15 21:48 ` Taylor Blau 2020-09-15 22:32 ` Junio C Hamano 2020-09-15 22:02 ` Jakub Narębski
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=CAPig+cQnnukVoJTgsu1sGFWkAYv7V38-0s-CgYuMyizYHhSFQQ@mail.gmail.com \ --to=sunshine@sunshineco.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
Git Mailing List Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/git/0 git/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 git git/ https://lore.kernel.org/git \ git@vger.kernel.org public-inbox-index git Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git