Re: [PATCH v8 07/18] luks2: Use more intuitive object name instead of json index in user messages

2020-12-12 Thread Patrick Steinhardt
On Tue, Dec 08, 2020 at 04:45:38PM -0600, Glenn Washburn wrote: > Use the object name in the json array rather than the 0 based index in the > json array for keyslots, segments, and digests. This is less confusing for > the end user. For example, say you have a LUKS2 device with a key in slot 1 > a

Re: [PATCH v8 07/18] luks2: Use more intuitive object name instead of json index in user messages

2020-12-09 Thread Daniel Kiper
On Tue, Dec 08, 2020 at 04:45:38PM -0600, Glenn Washburn wrote: > Use the object name in the json array rather than the 0 based index in the > json array for keyslots, segments, and digests. This is less confusing for > the end user. For example, say you have a LUKS2 device with a key in slot 1 > a

[PATCH v8 07/18] luks2: Use more intuitive object name instead of json index in user messages

2020-12-08 Thread Glenn Washburn
Use the object name in the json array rather than the 0 based index in the json array for keyslots, segments, and digests. This is less confusing for the end user. For example, say you have a LUKS2 device with a key in slot 1 and slot 4. When using the password for slot 4 to unlock the device, the

Re: [PATCH v7 06/17] luks2: Use more intuitive slot key instead of index in user messages

2020-12-08 Thread Glenn Washburn
On Mon, 7 Dec 2020 21:15:33 +0100 Daniel Kiper wrote: > On Fri, Dec 04, 2020 at 10:43:35AM -0600, Glenn Washburn wrote: > > Use the slot key name in the json array rather than the 0 based > > index in the json array for keyslots, segments, and digests. This > > is less confusing for the end user.

Re: [PATCH v7 06/17] luks2: Use more intuitive slot key instead of index in user messages

2020-12-07 Thread Daniel Kiper
On Fri, Dec 04, 2020 at 10:43:35AM -0600, Glenn Washburn wrote: > Use the slot key name in the json array rather than the 0 based index in the > json array for keyslots, segments, and digests. This is less confusing for > the end user. For example, say you have a LUKS2 device with a key in slot 1 >

Re: [PATCH v7 06/17] luks2: Use more intuitive slot key instead of index in user messages

2020-12-06 Thread Patrick Steinhardt
On Fri, Dec 04, 2020 at 10:43:35AM -0600, Glenn Washburn wrote: > Use the slot key name in the json array rather than the 0 based index in the > json array for keyslots, segments, and digests. This is less confusing for > the end user. For example, say you have a LUKS2 device with a key in slot 1 >

[PATCH v7 06/17] luks2: Use more intuitive slot key instead of index in user messages

2020-12-04 Thread Glenn Washburn
Use the slot key name in the json array rather than the 0 based index in the json array for keyslots, segments, and digests. This is less confusing for the end user. For example, say you have a LUKS2 device with a key in slot 1 and slot 4. When using the password for slot 4 to unlock the device, th

Re: [PATCH v6 02/12] luks2: Use more intuitive slot key instead of index in user messages.

2020-12-03 Thread Daniel Kiper
On Thu, Dec 03, 2020 at 01:24:18AM -0600, Glenn Washburn wrote: > On Wed, 2 Dec 2020 18:23:08 +0100 > Daniel Kiper wrote: > > > On Fri, Nov 27, 2020 at 03:03:34AM -0600, Glenn Washburn wrote: > > > Use the slot key name in the json array rather than the 0 based > > > index in the json array for ke

Re: [PATCH v6 02/12] luks2: Use more intuitive slot key instead of index in user messages.

2020-12-02 Thread Glenn Washburn
On Wed, 2 Dec 2020 18:23:08 +0100 Daniel Kiper wrote: > On Fri, Nov 27, 2020 at 03:03:34AM -0600, Glenn Washburn wrote: > > Use the slot key name in the json array rather than the 0 based > > index in the json array for keyslots, segments, and digests. This > > is less confusing for the end user.

Re: [PATCH v6 02/12] luks2: Use more intuitive slot key instead of index in user messages.

2020-12-02 Thread Daniel Kiper
On Fri, Nov 27, 2020 at 03:03:34AM -0600, Glenn Washburn wrote: > Use the slot key name in the json array rather than the 0 based index in the > json array for keyslots, segments, and digests. This is less confusing for > the end user. For example, say you have a LUKS2 device with a key in slot 1 >

[PATCH v6 02/12] luks2: Use more intuitive slot key instead of index in user messages.

2020-11-27 Thread Glenn Washburn
Use the slot key name in the json array rather than the 0 based index in the json array for keyslots, segments, and digests. This is less confusing for the end user. For example, say you have a LUKS2 device with a key in slot 1 and slot 4. When using the password for slot 4 to unlock the device, th

[PATCH v5 02/11] luks: Use more intuitive slot key instead of index in user messages.

2020-11-22 Thread Glenn Washburn
Use the slot key name in the json array rather than the 0 based index in the json array for keyslots, segments, and digests. This is less confusing for the end user. For example, say you have a LUKS2 device with a key in slot 1 and slot 4. When using the password for slot 4 to unlock the device, th

Re: user messages

2009-12-26 Thread Carles Pina i Estany
Hi, On Dec/26/2009, Robert Millan wrote: > On Sat, Dec 26, 2009 at 11:20:27AM +0100, Carles Pina i Estany wrote: > >cmd_linux = grub_register_command ("linux", grub_cmd_linux, > > -0, "Load linux."); > > +0, "Load a Linux kernel.

Re: user messages

2009-12-26 Thread Robert Millan
On Sat, Dec 26, 2009 at 11:20:27AM +0100, Carles Pina i Estany wrote: >cmd_linux = grub_register_command ("linux", grub_cmd_linux, > - 0, "Load linux."); > + 0, "Load a Linux kernel."); The construct "Linux kernel" is very ambig

user messages

2009-12-26 Thread Carles Pina i Estany
Hello, Find an attached patch. Linux should be always capitalized. All Linux loaders should have the same message: consistency, better LZMA and less work for translators. If you prefer another string tell me and I'll change. -- Carles Pina i Estany http://pinux.info === modified file