cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake | IRC logs: and | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
epony has joined #pypy
lesshaste has quit [Ping timeout: 268 seconds]
<cfbolz> Snow, snow!
steve_s has joined #pypy
Dejan_ has joined #pypy
Dejan_ is now known as Dejan
Atque has quit [Ping timeout: 255 seconds]
Atque has joined #pypy
jcea has joined #pypy
steve_s has quit [Quit: Client closed]
Dejan has quit [Quit: Leaving]
jcea has quit [Quit: jcea]
jcea1 has joined #pypy
jcea1 is now known as jcea
epony has quit [Quit: QUIT]
jcea has quit [Quit: jcea]
jcea has joined #pypy
<arigato> cfbolz: :-)
<LarstiQ> here too although it's already starting to degrade
<arigato> as much as I'm complaining, git has very cool lower-level layers. if I have the motivation I might one day do something that gives mercurial-style commands on top of the low-level git storage
<arigato> you'd get a mercurial-style command-line user interface, but still git & github
jcea has quit [Quit: jcea]
jcea1 has joined #pypy
jcea1 is now known as jcea
jcea has quit [Ping timeout: 256 seconds]
<antocuni> arigato: what you are describing sounds a lot like hggit, doesn't it?
<arigato> as far as I can tell, no, because hggit does not attempt to do the sane "mercurial" thing about either named branches or renames
<antocuni> I see
<arigato> and the low-level git is flexible enough that it should be possible and fun to implement it (without using hacks like adding special lines in the log messages)
<antocuni> yes, probably the same mechanism which is used by git-notes?
<arigato> no, unlikely, git-notes is used to store extra notes in a non-git-managed way
jinsun__ has joined #pypy
jinsun is now known as Guest7743
Guest7743 has quit [Killed ( (Nickname regained by services))]
jinsun__ is now known as jinsun