From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag.fr>,
git@vger.kernel.org, garciagj@ensimag.imag.fr,
"Matthieu Moy" <Matthieu.Moy@imag.fr>
Subject: Re: Contributing to git: cleaner git -rm & add configuration options
Date: Tue, 21 May 2013 09:35:10 -0700 [thread overview]
Message-ID: <7v38tgqojl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CALkWK0kV_wTbbb15SwVgxW5CVufqJgAjBifT_MwnJXR1-J+3JQ@mail.gmail.com> (Ramkumar Ramachandra's message of "Tue, 21 May 2013 12:50:42 +0530")
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> [+CC: Matthieu Moy]
>
> Mathieu Liénard--Mayor wrote:
>> -Cleaner error message when "git rm" fails with multiple files
>
> Should be fairly straightforward to implement. Just collect the
> errors and print them out at once.
>
>> -Add configuration options for some commonly used command-line options
>
> I'd really like status.short, status.branch, am.scissors and am.3way.
> Should be fairly straightforward to implement, although others might
> have different opinions on the names of the configuration variables.
>
> Also, I've taken the liberty to remove three ideas from the list:
> jk/fetch-always-update-tracking, vv/help-unknown-ref, and
> rr/rebase-autostash are already in `pu` and will hit `master` soon.
Matheiu, please ignore the "will hit 'master' soon" part. These
particular implementations might be ejected from 'pu' without
prejudice and discussed further.
But the idea is the same. Somebody have already been working on
them.
prev parent reply other threads:[~2013-05-21 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 5:42 Contributing to git: cleaner git -rm & add configuration options Mathieu Liénard--Mayor
2013-05-21 7:20 ` Ramkumar Ramachandra
2013-05-21 16:35 ` Junio C Hamano [this message]
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=7v38tgqojl.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=artagnon@gmail.com \
--cc=garciagj@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=mathieu.lienard--mayor@ensimag.fr \
/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).