Add .splice_read to sockets?
Hi! Is there any plans to make splice(socket, ..., pipe, ...) work? Thanks! -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Add .splice_read to sockets?
Hi! Is there any plans to make splice(socket, ..., pipe, ...) work? Thanks! -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key - my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Code snippet to reconstruct ancestry graph from bk repo
Replying to Roman Zippel:
> the "nitty-gritty" I was "whining" about and which is not available via
> bkcvs or bkweb and it's the most crucial information to make the bk data
> useful outside of bk. Larry was previously very clear about this that he
> considers this proprietary bk meta data and anyone attempting to export
> this information is in violation with the free bk licence, so you indeed
> just took the important parts and this is/was explicitly verboten for
> normal bk users.
(borrowed from Tommi Virtanen)
Code snippet to reconstruct ancestry graph from bk repo:
bk changes -end':I: $if(:PARENT:){:PARENT:$if(:MPARENT:){ :MPARENT:}}
$unless(:PARENT:){-}' |tac
format is:
newrev parent1 [parent2]
parent2 present if merge occurs.
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Code snippet to reconstruct ancestry graph from bk repo
Replying to Roman Zippel:
the nitty-gritty I was whining about and which is not available via
bkcvs or bkweb and it's the most crucial information to make the bk data
useful outside of bk. Larry was previously very clear about this that he
considers this proprietary bk meta data and anyone attempting to export
this information is in violation with the free bk licence, so you indeed
just took the important parts and this is/was explicitly verboten for
normal bk users.
(borrowed from Tommi Virtanen)
Code snippet to reconstruct ancestry graph from bk repo:
bk changes -end':I: $if(:PARENT:){:PARENT:$if(:MPARENT:){ :MPARENT:}}
$unless(:PARENT:){-}' |tac
format is:
newrev parent1 [parent2]
parent2 present if merge occurs.
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key - my pgp key
This message represents the official view of the voices in my head
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel SCM saga..
Replying to Linus Torvalds: > Ok, > as a number of people are already aware (and in some cases have been Actually, I'm very disappointed things gone such counter-productive way. All along the history, I was against Larry's opponents, but at the end, they are right. That's pity. To quote vin diesel' character Riddick, "there's no such word as friend", or something. Anyway, seems that folks in Canonical was aware about it, and here's the result of this awareness: http://bazaar-ng.org/ This need some testing though, along with really hard part - transfer all history, nonlinear ... I don't know how anyone can do this till 1 Jul 2005, sorry :( > PS. Don't bother telling me about subversion. If you must, start reading > up on "monotone". That seems to be the most viable alternative, but don't > pester the developers so much that they don't get any work done. They are > already aware of my problems ;) Monotone is good, but I don't really know limits of sqlite3 wrt kernel case. And again, what we need to do to retain history ... -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel SCM saga..
Replying to Linus Torvalds: Ok, as a number of people are already aware (and in some cases have been Actually, I'm very disappointed things gone such counter-productive way. All along the history, I was against Larry's opponents, but at the end, they are right. That's pity. To quote vin diesel' character Riddick, there's no such word as friend, or something. Anyway, seems that folks in Canonical was aware about it, and here's the result of this awareness: http://bazaar-ng.org/ This need some testing though, along with really hard part - transfer all history, nonlinear ... I don't know how anyone can do this till 1 Jul 2005, sorry :( PS. Don't bother telling me about subversion. If you must, start reading up on monotone. That seems to be the most viable alternative, but don't pester the developers so much that they don't get any work done. They are already aware of my problems ;) Monotone is good, but I don't really know limits of sqlite3 wrt kernel case. And again, what we need to do to retain history ... -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key - my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 1/1] /proc/$$/ipaddr and per-task networking bits
Replying to Arjan van de Ven: > On Thu, 2005-03-10 at 17:00 +0100, Lorenzo HernÃndez GarcÃa-Hierro > wrote: it tries to fill the > > ipaddr member of the task_struct structure with the IP address > > associated to the user running @current task/process,if available. > > but... a use doesn't hane an IP. a host does. I don't get it too With multihomed setup same process I have can send and receive on many addresses simultaneously. So single ip_addr cannot describe this situation. -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 1/1] /proc/$$/ipaddr and per-task networking bits
Replying to Arjan van de Ven: On Thu, 2005-03-10 at 17:00 +0100, Lorenzo Hernndez Garca-Hierro wrote: it tries to fill the ipaddr member of the task_struct structure with the IP address associated to the user running @current task/process,if available. but... a use doesn't hane an IP. a host does. I don't get it too With multihomed setup same process I have can send and receive on many addresses simultaneously. So single ip_addr cannot describe this situation. -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key - my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
