From: Sahil Dua <sahildua2305@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)
Date: Thu, 21 Sep 2017 23:14:54 +0200 [thread overview]
Message-ID: <CALiud+m1PAD8r0ygoUj3g4LzQjdoPu0CmjiejyG8pHOhr3Fk=Q@mail.gmail.com> (raw)
In-Reply-To: <xmqq8thgy03t.fsf@gitster.mtv.corp.google.com>
>
> * sd/branch-copy (2017-06-18) 3 commits
> - branch: add a --copy (-c) option to go with --move (-m)
> - branch: add test for -m renaming multiple config sections
> - config: create a function to format section headers
>
> "git branch" learned "-c/-C" to create and switch to a new branch
> by copying an existing one.
>
> I personally do not think "branch --copy master backup" while on
> "master" that switches to "backup" is a good UI, and I *will* say
> "I told you so" when users complain after we merge this down to
> 'master'.
Junio, what's up with this one? It's been a long time for this being
cooked in next. Do we have a plan/idea going forward or is it just
waiting for more feedback?
next prev parent reply other threads:[~2017-09-21 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:58 What's cooking in git.git (Sep 2017, #03; Fri, 15) Junio C Hamano
2017-09-15 7:50 ` Lars Schneider
2017-09-19 1:18 ` Junio C Hamano
2017-09-15 19:14 ` Johannes Schindelin
2017-09-15 20:33 ` Junio C Hamano
2017-09-15 19:23 ` Johannes Schindelin
2017-09-15 20:49 ` Junio C Hamano
2017-09-29 11:39 ` Johannes Schindelin
2017-09-21 21:14 ` Sahil Dua [this message]
2017-09-22 0:59 ` Junio C Hamano
2017-09-22 3:39 ` Junio C Hamano
2017-09-24 16:16 ` Sahil Dua
2017-09-25 0: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='CALiud+m1PAD8r0ygoUj3g4LzQjdoPu0CmjiejyG8pHOhr3Fk=Q@mail.gmail.com' \
--to=sahildua2305@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).