Re: Input for Contributions to FOSS Projects [was Re: losetup "size" parameter?]
Shlomi Fish wrote: That's not the case for Subversion ( http://subversion.tigris.org/ ). They generally commented on any patch I sent to the developer mailing list or bug tracker. Sometimes I had to revise my patch because of very small things, including trailing whitespace, or improper indentation. Subversion have a very specific user attitude policy in place, that more or less makes all core developers play nice with newbies and incidental contributers. In that respect, Subversion is the exception that proves the rule. Don't get me wrong, I think they have it right. It's just that, unfortunately, they are the exception (either that, or I personally hit particular difficult projects). Shachar = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Input for Contributions to FOSS Projects [was Re: losetup "size" parameter?]
Hi! On Thursday 17 April 2008, Shachar Shemesh wrote: > Oleg Goldshmidt wrote: > > On Thu, Apr 17, 2008 at 8:17 AM, Shachar Shemesh <[EMAIL PROTECTED]> wrote: > >> sending a > >> patch to a major component in Linux and getting a "good work" in reply > >> is definitely a welcome change. > > > > Let me venture a wild guess: maybe it *was* a good work? ;-) > > Even so, most major projects I know (Wine, Postgresql, Linux) the > highest form of compliment you are likely to receive is that they commit > your patch to the revision control. Getting actual feedback if it's good > is rare. Even getting actual feedback if it's bad isn't very common. > That's not the case for Subversion ( http://subversion.tigris.org/ ). They generally commented on any patch I sent to the developer mailing list or bug tracker. Sometimes I had to revise my patch because of very small things, including trailing whitespace, or improper indentation. Normally, I received a notification if a patch I sent was (finally) placed into the version control system, possibly with a thanks. I also received this: http://svn.haxx.se/dev/archive-2003-08/0476.shtml I later on stopped actively contributing patches to Subversion because I felt that it was already in very good shape, and no longer need my active help. Nevertheless, I still sometimes write patches for their links page to add a good link I'm encountering and send it (and it is either applied or dropped down). I really liked the online atmosphere of Subversion, and they certainly made co-developers or co-contributers welcome. I should also note that when I contributed patches to the perl5 (core) documents (perl*.pod) I normally received replies that requested me to correct typos, formatting style, trailing whitespace, etc. My patches were eventually applied, normally with a small thank you. My bug reports (which I am too incapable to fix myself, but was still capable enough to discover) were also usually dealt with. I had some other, less positive experiences, but don't recall them as vividly, and would rather not comment on them. Regards, Shlomi Fish - Shlomi Fish [EMAIL PROTECTED] Homepage:http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: losetup "size" parameter?
Oleg Goldshmidt wrote: On Thu, Apr 17, 2008 at 8:17 AM, Shachar Shemesh <[EMAIL PROTECTED]> wrote: sending a patch to a major component in Linux and getting a "good work" in reply is definitely a welcome change. Let me venture a wild guess: maybe it *was* a good work? ;-) Even so, most major projects I know (Wine, Postgresql, Linux) the highest form of compliment you are likely to receive is that they commit your patch to the revision control. Getting actual feedback if it's good is rare. Even getting actual feedback if it's bad isn't very common. Shachar = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Posix/NTPL : Is particular thread alive ? (pthread_timedjoin_np ??)
Lev Olshvang wrote: I am looking for generic way to ask about thread existence. You mean like calling pthread_kill() with a signal number of zero? :-) Gilad -- Gilad Ben-Yossef Chief Coffee Drinker Codefidence Ltd. The code is free, your time isn't.(TM) Web:http://codefidence.com Email: [EMAIL PROTECTED] Office: +972-8-9316883 ext. 201 Fax:+972-8-9316885 Mobile: +972-52-8260388
Re: losetup "size" parameter?
On Thu, Apr 17, 2008 at 8:17 AM, Shachar Shemesh <[EMAIL PROTECTED]> wrote: > sending a > patch to a major component in Linux and getting a "good work" in reply is > definitely a welcome change. Let me venture a wild guess: maybe it *was* a good work? ;-) -- Oleg Goldshmidt | [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Posix/NTPL : Is particular thread alive ? (pthread_timedjoin_np ??)
guy keren wrote: Lev Olshvang wrote: Hi friends, I seems that i have buggy implementation of pthread_timedjoin_np. Although linux does not documented this function yet ( see http://www.kernel.org/doc/man-pages/missing_pages.html ), I suspect that on my installation this function does not work properly because it returns sometimes 0, sometimes 110 and does not set errno to ETIMEOUT. After some googling I still do not know how to get thread status. As an idea i thought about using the futex() to check memory pointed my thread handle, but I am almost sure this solution (if pthread handle indeed references memory) is dirty, ... I saw on this list people with experience in thread programming and I am hope for you help. Cheers, Lev Hi Lev, why do you want to use this non-posix API in the first place? APIs ending with '_np' are not part of the pthreads spec - and thus are not portable and should be avoided. why can't you use the standard pthread_join API? and if you need a work-around you can use some portable mechanism, e.g. synchronizing using a condition variable, having the inner thread signal it just before terminating, and the outer thread waiting on it just before calling pthread_join? --guy Hi, I am looking for generic way to ask about thread existence. The problem is that I create thread for third party function, so I can not add to this function code to use thread signalling and cond variables. Yes, I know that _np functioins are GNU extensions to POSIX, but I did not found way to query thread aliviness. Thanks for answer. L. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: losetup "size" parameter?
On Thu, Apr 17, 2008 at 08:17:08AM +0300, Shachar Shemesh wrote: > I have to point out Karel Zak, the maintainer of util-linux-ng, as a > nice surprise. I am used to benevolent dictators/steering committee > members being somewhat on the rough side from many major FOSS projects, > and sending a patch to a major component in Linux and getting a "good > work" in reply is definitely a welcome change. I received a thank you from the maintainer of LIRC for sending him a new remote definition. Far different from some of my other experiences. Geoff. -- Geoffrey S. Mendelson, Jerusalem, Israel [EMAIL PROTECTED] N3OWJ/4X1GM = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
