On Mon, Mar 20, 2017 at 02:18:01PM -0400, Jeff King wrote:
> I think we've had similar proposals in the form of an
> environment variable like "GIT_PLUMBING" (and your "command",
> which I do like syntactically, would probably just end up
> setting such an environment variable anyway).
For referen
On Mon, Mar 20, 2017 at 7:56 PM, Junio C Hamano wrote:
> One thing we may want to consider is why we have to even worry about
> scripts getting broken. It is because people script around
> Porcelain, and that is because we have been too eager to improve
> Porcelain while neglecting plumbing for t
On Mon, Mar 20, 2017 at 11:56:35AM -0700, Junio C Hamano wrote:
> One thing we may want to consider is why we have to even worry about
> scripts getting broken. It is because people script around
> Porcelain, and that is because we have been too eager to improve
> Porcelain while neglecting plumb
Brandon Williams writes:
> If in the future we did want better support for making user defaults
> (apart from aliases) for commands we could entertain creating a command
> like bash's 'command' which ignores any user defaults and executes a
> particular command in a vanilla mode.
>
> So if the us
On Mon, Mar 20, 2017 at 10:32:37AM -0700, Brandon Williams wrote:
> > > IIRC the consensus was that such a facility would allow commands or
> > > individual options to say "this command/option is configurable", thus
> > > of course all plumbing utilities would be unconfigurable, but
> > > porcelai
On 03/20, Duy Nguyen wrote:
> On Sun, Mar 19, 2017 at 8:43 PM, Ævar Arnfjörð Bjarmason
> wrote:
> > On Sun, Mar 19, 2017 at 2:18 PM, brian m. carlson
> > wrote:
> >> On Sun, Mar 19, 2017 at 11:15:33AM +0100, Matthieu Moy wrote:
> >>> I think the main problem is indeed "stop the users from shootin
On Sun, Mar 19, 2017 at 8:18 PM, brian m. carlson
wrote:
>> OTOH, we already have almost "enable such or such option by default"
>> with aliases. People who always run "git am" with "-3" can write
>>
>> [alias]
>> a3 = am -3
>>
>> and just run "git a3".
>
> I tend to agree here.
That's ex
On Sun, Mar 19, 2017 at 8:43 PM, Ævar Arnfjörð Bjarmason
wrote:
> On Sun, Mar 19, 2017 at 2:18 PM, brian m. carlson
> wrote:
>> On Sun, Mar 19, 2017 at 11:15:33AM +0100, Matthieu Moy wrote:
>>> I think the main problem is indeed "stop the users from shooting
>>> themselves in the foot". Many comm
On Sun, Mar 19, 2017 at 2:18 PM, brian m. carlson
wrote:
> On Sun, Mar 19, 2017 at 11:15:33AM +0100, Matthieu Moy wrote:
>> I think the main problem is indeed "stop the users from shooting
>> themselves in the foot". Many command-line options change the behavior
>> completely so allowing users to
On Sun, Mar 19, 2017 at 11:15:33AM +0100, Matthieu Moy wrote:
> I think the main problem is indeed "stop the users from shooting
> themselves in the foot". Many command-line options change the behavior
> completely so allowing users to enable them by default means allowing
> the users to change Git
Duy Nguyen writes:
> On Thu, Feb 19, 2015 at 5:32 PM, Matthieu Moy
> wrote:
>> +### Add configuration options for some commonly used command-line options
>> +
>> +This includes:
>> +
>> +* git am -3
>> +
>> +* git am -c
>> +
>> +Some
On Thu, Feb 19, 2015 at 5:32 PM, Matthieu Moy
wrote:
> +### Add configuration options for some commonly used command-line options
> +
> +This includes:
> +
> +* git am -3
> +
> +* git am -c
> +
> +Some people always run the command with these options, and would
>
Koosha Khajehmoogahi writes:
> This patch adds a 'showmerges' config. option for git-log.
> This option determines whether the log should contain merge
> commits or not. In essence, if this option is set to true,
> git-log will be run as 'git-log --no-merges'.
>
> Signed-off-by: Koosha Khajehmoog
On 03/15/2015 08:29 PM, Koosha Khajehmoogahi wrote:
> This patch adds a 'showmerges' config. option for git-log.
> This option determines whether the log should contain merge
> commits or not. In essence, if this option is set to true,
Sorry, this should be 'false'.
> git-log will be run as 'gi
This patch adds a 'showmerges' config. option for git-log.
This option determines whether the log should contain merge
commits or not. In essence, if this option is set to true,
git-log will be run as 'git-log --no-merges'.
Signed-off-by: Koosha Khajehmoogahi
---
Documentation/config.txt | 3 +++
Koosha Khajehmoogahi writes:
> Does this microproject require the feature to be a generic one for every
> possible command or should it be limited to some particular commands?
The Micro is written lazily so that by writing that entry once, it
can tell many students to work on many different Git
Does this microproject require the feature to be a generic one for every
possible command or should it be limited to some particular commands?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
17 matches
Mail list logo
