Gerhard Mack wrote:
ata1.00: configured for UDMA/100
[...]
ata1.00: configured for UDMA/66
[...]
ata1.00: configured for UDMA/44
[...]
ata1.00: configured for UDMA/33
[...]
ata1.00: configured for UDMA/25
[...]
ata1.00: configured for UDMA/16
[...]
ata1.00: configured for PIO4
I have the same
Ralf Müller wrote:
I had the same type of problem using an unstable power supply - after
replacing it the problems
were gone ...
Hm.. my shuttle box has only a 350W power supply, that could indeed be
the problem, as I have an Athlon 64 X2 4400+ CPU (dual core), two
SATA-II 500GB harddrives
echo disk /sys/power/state
successfully saves that state to the disk, but just as the laptop is
about to turn itself off, it reboots (successfully, so the
hibernation/resume process works well, even with X running! which is
awesome :) ). But I'd rather like the computer turned off after I
CC: lkml, because that's a question anyone familiar with the driver
subsystem can answer.
Dmitry Torokhov wrote:
On Nov 15, 2007 9:20 AM, Tomas Carnecky [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
No, sorry. Current object lifetime rules require input devices (as
well as platform devices
Pavel Machek wrote:
Hi!
echo disk /sys/power/state
successfully saves that state to the disk, but just as the laptop is
about to turn itself off, it reboots (successfully, so the
hibernation/resume process works well, even with X running! which is
awesome :) ). But I'd rather like the
Tomas Carnecky wrote:
Pavel Machek wrote:
Hi!
echo disk /sys/power/state
successfully saves that state to the disk, but just as the laptop is
about to turn itself off, it reboots (successfully, so the
hibernation/resume process works well, even with X running! which is
awesome
Pavel Machek wrote:
Hi!
echo disk /sys/power/state
successfully saves that state to the disk, but just as the laptop is
about to turn itself off, it reboots (successfully, so the
hibernation/resume process works well, even with X running! which is
awesome :) ). But I'd rather like the
Since this is becoming more an IDE/ATA issue, I added
[EMAIL PROTECTED] to CC. I hope that's the right mailinglist.
Tomas Carnecky wrote:
(3) Once the notebook was in the docking station (whether I boot it
while in the dock or boot it outside and then put it into the dock) and
I take it out
Roel Kluin wrote:
First of all, is /sound/oss/* still maintained?
Documentation/feature-removal-schedule.txt
What: drivers depending on OSS_OBSOLETE
When: options in 2.6.23, code in 2.6.25
Why: obsolete OSS drivers
Who: Adrian Bunk [EMAIL PROTECTED]
tom
-
To unsubscribe from this list:
WARNING: at arch/x86/kernel/smp_64.c:427 smp_call_function_single()
WARNING: at arch/x86/kernel/smp_64.c:397 smp_call_function_mask()
dmesg and config attached.
I'm getting about three of each at boot. I'm running:
commit e1cca7e8d484390169777b423a7fe46c7021fec1
Date: Thu Nov 29 16:25:29 2007
Arjan van de Ven wrote:
On Sun, 02 Dec 2007 09:43:39 +0100
Tomas Carnecky [EMAIL PROTECTED] wrote:
WARNING: at arch/x86/kernel/smp_64.c:427 smp_call_function_single()
WARNING: at arch/x86/kernel/smp_64.c:397 smp_call_function_mask()
dmesg and config attached.
I'm getting about three
Rafael J. Wysocki wrote:
On Sunday, 18 of November 2007, Tomas Carnecky wrote:
Pavel Machek wrote:
Hi!
echo disk /sys/power/state
successfully saves that state to the disk, but just as the laptop is
about to turn itself off, it reboots (successfully, so the
hibernation/resume process
Cyrill Gorcunov wrote:
[=?ISO-8859-1?Q?J=F6rn_Engel_ - Thu, Jan 03, 2008 at 12:29:57PM +0100]
| On Thu, 3 January 2008 14:19:25 +0300, Cyrill Gorcunov wrote:
| @@ -232,7 +232,8 @@ void audit_log_lost(const char *message)
|
| if (print) {
| printk(KERN_WARNING
| -
Christer Weinigel wrote:
By the way, what is the consensus on lines over 80 characters?
checkpatch complains about the following:
WARNING: line over 80 characters
#762: FILE: drivers/spi/spi_s3c24xx_dma.c:720:
+ printk(KERN_INFO S3C24xx SPI DMA driver (c) 2007 Nordnav Technologies
AB\n);
Linus Torvalds wrote:
The fact is, I've _always_ considered the desktop to be the most important
part. And I suspect that that actually is true for most kernel developers,
because quite frankly, that's what 99% of them ends up using. If a kernel
developer uses Windows for his day-to-day work,
Jens Axboe wrote:
diff --git a/Documentation/RCU/checklist.txt b/Documentation/RCU/checklist.txt
index f4dffad..36d6185 100644
--- a/Documentation/RCU/checklist.txt
+++ b/Documentation/RCU/checklist.txt
@@ -259,3 +259,16 @@ over a rather long period of time, but improvements are
always
Dirk wrote:
How about having a simple Game API like SDL included in the Kernel and
officially announce the promise to change it only once every couple of
years?
A new API would be counter-productive! There's X11/OpenGL for graphics
and OpenAL for sound, both APIs widespread even in the
Gert Vervoort wrote:
When I try to use oprofile on 2.6.19, it does not seem to work:
http://lkml.org/lkml/2006/11/22/172
tom
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Gert Vervoort wrote:
When I try to use oprofile on 2.6.19, it does not seem to work:
[EMAIL PROTECTED] tmp]$ sudo opcontrol --no-vmlinux
[EMAIL PROTECTED] tmp]$ sudo opcontrol --start
/usr/bin/opcontrol: line 911: /dev/oprofile/0/enabled: No such file or
directory/usr/bin/opcontrol: line
Alexey Dobriyan wrote:
On Fri, Dec 15, 2006 at 09:20:58PM +, James Porter wrote:
For what it's worth, I don't see any problem with binary drivers from hardware
manufacturers.
Binary drivers from hardware manufacturers are crap. Learn it by heart.
That's your personal opinion! A lot
Erik Mouw wrote:
However, we thought the legal and technical expense involved in
writing this binary driver and possibly violating the Linux kernel
copyright was well spend.
So Microsoft is right, the legal status of Linux software _is_ unclear.
You just gave them every reason to continue
James Porter wrote:
I'm pretty sure Linus has decided, basically he said the patches to
prevent non-gpl binary drivers are not going into his tree unless every
other tree adopts it. Of course the few supporting won't get off their
high horse and try it on a different tree.
.. unfortunately,
Gert Vervoort wrote:
Tomas Carnecky wrote:
Gert Vervoort wrote:
When I try to use oprofile on 2.6.19, it does not seem to work:
http://lkml.org/lkml/2006/11/22/172
Disabling the nmi watchdog, as suggested in:
http://marc.theaimsgroup.com/?l=oprofile-listm=116422889324043w=2,
also makes
Eric Dumazet wrote:
On Thursday 11 January 2007 15:37, Tomas Carnecky wrote:
Gert Vervoort wrote:
Tomas Carnecky wrote:
Gert Vervoort wrote:
When I try to use oprofile on 2.6.19, it does not seem to work:
http://lkml.org/lkml/2006/11/22/172
Disabling the nmi watchdog, as suggested in:
http
Russell King wrote:
On Thu, Jan 18, 2007 at 01:58:52PM +0100, Bernhard Walle wrote:
-static char command_line[COMMAND_LINE_SIZE];
+static char __initdata command_line[COMMAND_LINE_SIZE];
Uninitialised data is placed in the BSS. Adding __initdata to BSS
data causes grief.
Static
I only have a screenshot with no backtrace, if you want to see the
function names in the backtrace, please tell me what I need to do.
http://dbservice.com/ftpdir/tom/kernel-bug.jpg
I was running a 2.6.19-ge??? kernel before (I don't remember which
version exactly) and it was running fine, today
Jiri Kosina wrote:
On Tue, 19 Feb 2008, Tomas Carnecky wrote:
usb 1-2.2: new full speed USB device using ehci_hcd and address 6
usb 1-2.2: configuration #1 chosen from 1 choice
HID device claimed by neither input, hiddev nor hidraw
input: Logitech Z-10 USB Speaker as
/devices/pci:00/
kernel 2.6.25-rc2
usb 1-2.2: new full speed USB device using ehci_hcd and address 6
usb 1-2.2: configuration #1 chosen from 1 choice
HID device claimed by neither input, hiddev nor hidraw
input: Logitech Z-10 USB Speaker as
/devices/pci:00/:00:02.1/usb1/1-2/1-2.2/1-2.2:1.3/input/input4
Jiri Kosina wrote:
On Tue, 19 Feb 2008, Tomas Carnecky wrote:
The device apparently has four 'interfaces' - whatever that is, see [1].
It seems like usbhid probes interface 2 (which is the LCD plus a few
buttons, probably the four just under the LCD, as described [1]).
Because usbhid doesn't
Jiri Kosina wrote:
Does anything appear in dmesg when you press those buttons? There should
be messages resembling the one you already have there:
drivers/hid/hid-core.c: report (size 8) (unnumbered)
drivers/hid/hid-core.c: report 0 (size 8) = 00 00 28 00 00 00 00 00
and they should react to
Lukas Hejtmanek wrote:
On Mon, Feb 25, 2008 at 06:01:13PM -0300, Henrique de Moraes Holschuh wrote:
Not even over the new netlink socket? Or the thinkpad-acpi input device?
how can I check this?
A while ago I worked on a new acpi daemon that could receive events from
both netlink and
Jon Masters wrote:
need a technological mechanism here to enforce the obvious. To me, it
just seems totally obvious (any legal comment?) that early C string
termination is undermining the intent of the MODULE_LICENSE tag.
I completely agree with that. It's like I sign a contract and the
On Mon, 23 Jul 2012 22:08:48 -0700, Junio C Hamano gits...@pobox.com wrote:
* The value of core.attributesfile and core.excludesfile default to
$HOME/.config/attributes and $HOME/.config/ignore respectively when
these files exist.
$HOME/.config/git/attributes ..
--
To unsubscribe from
Kernel 2.6.22-rc2-g47b97135, happened while running wine (32bit app) on
my amd64 box... should I try -rc3?
BUG: at mm/slab.c:777 __find_general_cachep()
Call Trace:
[80278146] __kmalloc+0xa6/0xe0
[802ac959] compat_core_sys_select+0x109/0x290
[802ae3f1]
Despite it's a Microsoft product, it's actually very nice and useful. A
little pad with a few buttons and connectors for a headset. It's an USB
device, but it doesn't represent itself as an input/HID device:
HID device not claimed by input or hiddev
I plugged it into a windows box and the USB
Jiri Kosina wrote:
On Thu, 17 May 2007, Tomas Carnecky wrote:
Despite it's a Microsoft product, it's actually very nice and useful. A
little pad with a few buttons and connectors for a headset. It's an USB
device, but it doesn't represent itself as an input/HID device:
HID device
Additional info: HID device has two collections (whatever those are, I
have _no_ idea):
collection 00: type: 1, usage: 000b0005, level:
collection 01: type: 2, usage: 0008003a, level: 0001
The usage of the first one means 'Telephony/Headset', the second one
'LEDs/Usage Selected
Jiri Kosina wrote:
We don't want neither the 'Telephony' nor 'LEDs' usages to be claimed by
the hid-input system, that seems to make a little sense.
I changed the IS_INPUT_APPLICATION() macro to accept 'Telephony/Headset'
and now the kernel has created a new event device node for the device
Jiri Kosina wrote:
On Fri, 18 May 2007, Tomas Carnecky wrote:
GameVoice is used for VoIP communication between players. It consists of
a software and the small pad with eight buttons and connectors for the
headset. One of the buttons can be used to mute the microphone, the
others
Jiri Kosina wrote:
On Fri, 18 May 2007, Lee Revell wrote:
Despite it's a Microsoft product, it's actually very nice and useful. A
little pad with a few buttons and connectors for a headset. It's an USB
device, but it doesn't represent itself as an input/HID device:
HID device not claimed
Jiri Kosina wrote:
On Sat, 19 May 2007, Tomas Carnecky wrote:
I already thought about this option (to whitelist this particular
vendor/device ID as an hid-input device), but I first wanted some
feedback on the whole situation. As for the patch, I have zero knowledge
of the hid subsystem
Erik Mouw wrote:
"However, we thought the legal and technical expense involved in
writing this binary driver and possibly violating the Linux kernel
copyright was well spend."
So Microsoft is right, the legal status of Linux software _is_ unclear.
You just gave them every reason to
James Porter wrote:
I'm pretty sure Linus has decided, basically he said the patches to
prevent non-gpl binary drivers are not going into his tree unless every
other tree adopts it. Of course the few supporting won't get off their
high horse and try it on a different tree.
.. unfortunately,
Jens Axboe wrote:
> diff --git a/Documentation/RCU/checklist.txt b/Documentation/RCU/checklist.txt
> index f4dffad..36d6185 100644
> --- a/Documentation/RCU/checklist.txt
> +++ b/Documentation/RCU/checklist.txt
> @@ -259,3 +259,16 @@ over a rather long period of time, but improvements are
>
Dirk wrote:
>
> How about having a simple Game API like SDL included in the Kernel and
> officially announce the promise to change it only once every couple of
> years?
>
A new API would be counter-productive! There's X11/OpenGL for graphics
and OpenAL for sound, both APIs widespread even in
Gert Vervoort wrote:
>
> When I try to use oprofile on 2.6.19, it does not seem to work:
>
http://lkml.org/lkml/2006/11/22/172
tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Gert Vervoort wrote:
>
> When I try to use oprofile on 2.6.19, it does not seem to work:
>
> [EMAIL PROTECTED] tmp]$ sudo opcontrol --no-vmlinux
> [EMAIL PROTECTED] tmp]$ sudo opcontrol --start
> /usr/bin/opcontrol: line 911: /dev/oprofile/0/enabled: No such file or
>
Gert Vervoort wrote:
> Tomas Carnecky wrote:
>> Gert Vervoort wrote:
>>> When I try to use oprofile on 2.6.19, it does not seem to work:
>>>
>> http://lkml.org/lkml/2006/11/22/172
>>
> Disabling the nmi watchdog, as suggested in:
> http://marc.theaim
Eric Dumazet wrote:
> On Thursday 11 January 2007 15:37, Tomas Carnecky wrote:
>> Gert Vervoort wrote:
>>> Tomas Carnecky wrote:
>>>> Gert Vervoort wrote:
>>>>> When I try to use oprofile on 2.6.19, it does not seem to work:
>>>> http://lk
I only have a screenshot with no backtrace, if you want to see the
function names in the backtrace, please tell me what I need to do.
http://dbservice.com/ftpdir/tom/kernel-bug.jpg
I was running a 2.6.19-ge??? kernel before (I don't remember which
version exactly) and it was running fine, today
Alexey Dobriyan wrote:
On Fri, Dec 15, 2006 at 09:20:58PM +, James Porter wrote:
For what it's worth, I don't see any problem with binary drivers from hardware
manufacturers.
Binary drivers from hardware manufacturers are crap. Learn it by heart.
That's your personal opinion! A lot
Gerhard Mack wrote:
ata1.00: configured for UDMA/100
[...]
ata1.00: configured for UDMA/66
[...]
ata1.00: configured for UDMA/44
[...]
ata1.00: configured for UDMA/33
[...]
ata1.00: configured for UDMA/25
[...]
ata1.00: configured for UDMA/16
[...]
ata1.00: configured for PIO4
I have the same
Ralf Müller wrote:
I had the same type of problem using an unstable power supply - after
replacing it the problems
were gone ...
Hm.. my shuttle box has only a 350W power supply, that could indeed be
the problem, as I have an Athlon 64 X2 4400+ CPU (dual core), two
SATA-II 500GB harddrives
Russell King wrote:
> On Thu, Jan 18, 2007 at 01:58:52PM +0100, Bernhard Walle wrote:
>> -static char command_line[COMMAND_LINE_SIZE];
>> +static char __initdata command_line[COMMAND_LINE_SIZE];
>
> Uninitialised data is placed in the BSS. Adding __initdata to BSS
> data causes grief.
>
Jon Masters wrote:
> need a technological mechanism here to enforce the obvious. To me, it
> just seems totally obvious (any legal comment?) that early C string
> termination is undermining the intent of the MODULE_LICENSE tag.
>
I completely agree with that. It's like I sign a contract and the
Additional info: HID device has two collections (whatever those are, I
have _no_ idea):
collection 00: type: 1, usage: 000b0005, level:
collection 01: type: 2, usage: 0008003a, level: 0001
The usage of the first one means 'Telephony/Headset', the second one
'LEDs/Usage Selected
Jiri Kosina wrote:
> We don't want neither the 'Telephony' nor 'LEDs' usages to be claimed by
> the hid-input system, that seems to make a little sense.
I changed the IS_INPUT_APPLICATION() macro to accept 'Telephony/Headset'
and now the kernel has created a new event device node for the device
Jiri Kosina wrote:
> On Fri, 18 May 2007, Tomas Carnecky wrote:
>> GameVoice is used for VoIP communication between players. It consists of
>> a software and the small pad with eight buttons and connectors for the
>> headset. One of the buttons can be used to mute the micro
Jiri Kosina wrote:
> On Fri, 18 May 2007, Lee Revell wrote:
>
>>> Despite it's a Microsoft product, it's actually very nice and useful. A
>>> little pad with a few buttons and connectors for a headset. It's an USB
>>> device, but it doesn't represent itself as an input/HID device:
>>>HID
Jiri Kosina wrote:
> On Sat, 19 May 2007, Tomas Carnecky wrote:
>> I already thought about this option (to whitelist this particular
>> vendor/device ID as an hid-input device), but I first wanted some
>> feedback on the whole situation. As for the patch, I have zero kn
Kernel 2.6.22-rc2-g47b97135, happened while running wine (32bit app) on
my amd64 box... should I try -rc3?
BUG: at mm/slab.c:777 __find_general_cachep()
Call Trace:
[] __kmalloc+0xa6/0xe0
[] compat_core_sys_select+0x109/0x290
[] compat_sys_select+0xe1/0x190
[] cstar_do_call+0x1b/0x65
tom
-
Despite it's a Microsoft product, it's actually very nice and useful. A
little pad with a few buttons and connectors for a headset. It's an USB
device, but it doesn't represent itself as an input/HID device:
HID device not claimed by input or hiddev
I plugged it into a windows box and the USB
Jiri Kosina wrote:
> On Thu, 17 May 2007, Tomas Carnecky wrote:
>
>> Despite it's a Microsoft product, it's actually very nice and useful. A
>> little pad with a few buttons and connectors for a headset. It's an USB
>> device, but it doesn't represent itself as an inp
Linus Torvalds wrote:
The fact is, I've _always_ considered the desktop to be the most important
part. And I suspect that that actually is true for most kernel developers,
because quite frankly, that's what 99% of them ends up using. If a kernel
developer uses Windows for his day-to-day work,
CC: lkml, because that's a question anyone familiar with the driver
subsystem can answer.
Dmitry Torokhov wrote:
> On Nov 15, 2007 9:20 AM, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
>> Dmitry Torokhov wrote:
>>> No, sorry. Current object lifetime rules require in
Pavel Machek wrote:
> Hi!
>
>> echo disk > /sys/power/state
>>
>> successfully saves that state to the disk, but just as the laptop is
>> about to turn itself off, it reboots (successfully, so the
>> hibernation/resume process works well, even with X running! which is
>> awesome :) ). But I'd
Tomas Carnecky wrote:
> Pavel Machek wrote:
>> Hi!
>>
>>> echo disk > /sys/power/state
>>>
>>> successfully saves that state to the disk, but just as the laptop is
>>> about to turn itself off, it reboots (successfully, so the
>>> hi
Pavel Machek wrote:
> Hi!
>
>> echo disk > /sys/power/state
>>
>> successfully saves that state to the disk, but just as the laptop is
>> about to turn itself off, it reboots (successfully, so the
>> hibernation/resume process works well, even with X running! which is
>> awesome :) ). But I'd
Since this is becoming more an IDE/ATA issue, I added
[EMAIL PROTECTED] to CC. I hope that's the right mailinglist.
Tomas Carnecky wrote:
> (3) Once the notebook was in the docking station (whether I boot it
> while in the dock or boot it outside and then put it into the dock) and
> I ta
Rafael J. Wysocki wrote:
> On Sunday, 18 of November 2007, Tomas Carnecky wrote:
>> Pavel Machek wrote:
>>> Hi!
>>>
>>>> echo disk > /sys/power/state
>>>>
>>>> successfully saves that state to the disk, but just as the lap
echo disk > /sys/power/state
successfully saves that state to the disk, but just as the laptop is
about to turn itself off, it reboots (successfully, so the
hibernation/resume process works well, even with X running! which is
awesome :) ). But I'd rather like the computer turned off after I
Lukas Hejtmanek wrote:
On Mon, Feb 25, 2008 at 06:01:13PM -0300, Henrique de Moraes Holschuh wrote:
Not even over the new netlink socket? Or the thinkpad-acpi input device?
how can I check this?
A while ago I worked on a new acpi daemon that could receive events from
both netlink and
Cyrill Gorcunov wrote:
[=?ISO-8859-1?Q?J=F6rn_Engel_ - Thu, Jan 03, 2008 at 12:29:57PM +0100]
| On Thu, 3 January 2008 14:19:25 +0300, Cyrill Gorcunov wrote:
| > @@ -232,7 +232,8 @@ void audit_log_lost(const char *message)
| >
| > if (print) {
| > printk(KERN_WARNING
| > -
Christer Weinigel wrote:
By the way, what is the consensus on lines over 80 characters?
checkpatch complains about the following:
WARNING: line over 80 characters
#762: FILE: drivers/spi/spi_s3c24xx_dma.c:720:
+ printk(KERN_INFO "S3C24xx SPI DMA driver (c) 2007 Nordnav Technologies
Roel Kluin wrote:
> First of all, is /sound/oss/* still maintained?
>
Documentation/feature-removal-schedule.txt
What: drivers depending on OSS_OBSOLETE
When: options in 2.6.23, code in 2.6.25
Why: obsolete OSS drivers
Who: Adrian Bunk <[EMAIL PROTECTED]>
tom
-
To unsubscribe from this
WARNING: at arch/x86/kernel/smp_64.c:427 smp_call_function_single()
WARNING: at arch/x86/kernel/smp_64.c:397 smp_call_function_mask()
dmesg and config attached.
I'm getting about three of each at boot. I'm running:
commit e1cca7e8d484390169777b423a7fe46c7021fec1
Date: Thu Nov 29 16:25:29 2007
Arjan van de Ven wrote:
> On Sun, 02 Dec 2007 09:43:39 +0100
> Tomas Carnecky <[EMAIL PROTECTED]> wrote:
>
>> WARNING: at arch/x86/kernel/smp_64.c:427 smp_call_function_single()
>> WARNING: at arch/x86/kernel/smp_64.c:397 smp_call_function_mask()
>>
>> dmesg
Jiri Kosina wrote:
On Tue, 19 Feb 2008, Tomas Carnecky wrote:
usb 1-2.2: new full speed USB device using ehci_hcd and address 6
usb 1-2.2: configuration #1 chosen from 1 choice
HID device claimed by neither input, hiddev nor hidraw
input: Logitech Z-10 USB Speaker as
/devices/pci:00/
kernel 2.6.25-rc2
usb 1-2.2: new full speed USB device using ehci_hcd and address 6
usb 1-2.2: configuration #1 chosen from 1 choice
HID device claimed by neither input, hiddev nor hidraw
input: Logitech Z-10 USB Speaker as
/devices/pci:00/:00:02.1/usb1/1-2/1-2.2/1-2.2:1.3/input/input4
Jiri Kosina wrote:
On Tue, 19 Feb 2008, Tomas Carnecky wrote:
The device apparently has four 'interfaces' - whatever that is, see [1].
It seems like usbhid probes interface 2 (which is the LCD plus a few
buttons, probably the four just under the LCD, as described [1]).
Because usbhid doesn't
Jiri Kosina wrote:
Does anything appear in dmesg when you press those buttons? There should
be messages resembling the one you already have there:
drivers/hid/hid-core.c: report (size 8) (unnumbered)
drivers/hid/hid-core.c: report 0 (size 8) = 00 00 28 00 00 00 00 00
and they should react to
On Mon, 23 Jul 2012 22:08:48 -0700, Junio C Hamano wrote:
> * The value of core.attributesfile and core.excludesfile default to
>$HOME/.config/attributes and $HOME/.config/ignore respectively when
>these files exist.
$HOME/.config/git/attributes ..
--
To unsubscribe from this list: send
82 matches
Mail list logo