Michael Plante wrote:
> >> 2. They require invoking git during make, which of course means that if
> >> you're building from MSVC or WDK, this whole versioning falls apart.
>
> Can you add the fields to the struct, but leave them blank in this case?
Absolutely, libusb.git sets describe to the emp
Pete Batard wrote:
>> 2. They require invoking git during make, which of course means that if
>> you're building from MSVC or WDK, this whole versioning falls apart.
Can you add the fields to the struct, but leave them blank in this case? If
so, what is the downside of doing that?
Michael
Le dimanche 22 avril 2012 14:52:19, Pete Batard a écrit :
> but we also have to acknowledge that we are a minority.
I didn't know that. Maybe I overlooked mails, or wasn't subscribed to libusbx-
devel early enough... Or it was discussed in some other place.
I think it should be explained on the w
Pete Batard wrote:
> Also, if say you're using TortoiseGit on Windows to fetch the repo,
> and compile in a MinGW environment where git is not available (since
> git isn't installed by default there), you will fail to populate the
> last field.
Yes. As you all know I like to optimize for the commo
On Sun, Apr 22, 2012 at 8:51 PM, Pete Batard wrote:
> On 2012.04.21 07:24, Xiaofan Chen wrote:
>>> On 2012.04.14 02:09, Xiaofan Chen wrote:
[PATCH 16/37] Fix context memory leak in libusb_init()
http://libusb.6.n5.nabble.com/PATCH-16-37-Fix-context-memory-leak-in-libusb-init-td9623.html
On 2012.04.21 09:47, Hans de Goede wrote:
>> Next, I'd like to pick up the "Linux: Search for
>> /dev/usbdev. USB device special files" [1] patch, but
>> before I do that, I wouldn't mind if the Linux people get a chance to
>> look at it.
>
> I just reviewed the patch as found in git.libusb.org/lib
On 2012.04.22 10:27, Vincent Pelletier wrote:
>> I'd have libusbx everywhere, starting with soname, header
>> name, directory names, as well as API prefixes.
>
> I think this would be The Right Way (tm).
I think we share the same view here, but we also have to acknowledge
that we are a minority.
On 2012.04.21 07:24, Xiaofan Chen wrote:
>> On 2012.04.14 02:09, Xiaofan Chen wrote:
>>> [PATCH 16/37] Fix context memory leak in libusb_init()
>>> http://libusb.6.n5.nabble.com/PATCH-16-37-Fix-context-memory-leak-in-libusb-init-td9623.html
>>>
>>> [PATCH 15/37] log functions can be called before l
On 2012.04.22 09:26, Ludovic Rousseau wrote:
> I created a custom CSS for the libusbx wiki. It is at [1].
>
> So you do not have to use something like:
> === '''title''' ===
> to have the level 3 title in bold.
>
> Instead just use:
> === title ===
>
> Do not mix content and form. Form in the CSS,
(replying to both mails)
On Sun, Apr 22, 2012 at 3:24 AM, Pete Batard wrote:
> (but then again, does there exist a non-hostile fork?)
Management-wise, I'm convinced it indeed doesn't exist. It takes some
serious motivation to spend time to create a fork and gather a team
behind it, which should
On 4/21/12 19:36, "Peter Stuge" wrote:
>On Windows and Mac OS X I agree with you and Orin, because there are
>few (no?) useful system-wide package managers. On Linux and BSD there
>is generally a reliable package manager which handles dependencies,
>thus avoiding the problem. I of course understan
Hello,
I created a custom CSS for the libusbx wiki. It is at [1].
So you do not have to use something like:
=== '''title''' ===
to have the level 3 title in bold.
Instead just use:
=== title ===
Do not mix content and form. Form in the CSS, content in the wiki page.
If you want to improve/chang
12 matches
Mail list logo
