Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. Re: Openmoko Bug #2174: stable-tracking/16e183d:
      jbt6k74.c:558:    error: implicit declaration of function
      'jbt6k74_display_onoff' (Openmoko Public Trac)
   2. Re: Openmoko Bug #2174: stable-tracking/16e183d:
      jbt6k74.c:558:    error: implicit declaration of function
      'jbt6k74_display_onoff' (Openmoko Public Trac)
   3. Re: Openmoko Bug #2174: stable-tracking/16e183d:
      jbt6k74.c:558:    error: implicit declaration of function
      'jbt6k74_display_onoff' (Openmoko Public Trac)
   4. Re: Openmoko Bug #2174: stable-tracking/16e183d:
      jbt6k74.c:558:    error: implicit declaration of function
      'jbt6k74_display_onoff' (Openmoko Public Trac)
   5. Re: Openmoko Bug #2165: gtk layout differences between 2007.2
      and       2008.testing (Openmoko Public Trac)
--- Begin Message ---
#2174: stable-tracking/16e183d: jbt6k74.c:558: error: implicit declaration of
function 'jbt6k74_display_onoff'
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                 
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:  always         
-----------------------------+----------------------------------------------

Comment(by andy):

 Yes git diff is the only tool I know about for this as well.

 Before we changed to having trees with history, you could actually see
 stable-tracking head if you scrolled down from andy-tracking head, then
 you knew what the additional patchset was.  But with the history, that is
 hidden and the branches publicly sync by merge patches that are mini git
 diffs.  I think between the two choices having the history is going to be
 generally more useful but your point is fair enough.

 I still have that kind of branch here locally, I can publish it in
 addition to the history branches but probably it will make some peoples'
 heads explode to see two branches for each official one.

 For now stable-tracking is just a stake in the ground for a future where
 we got everything upstream, I am only building andy-tracking regularly.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2174#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2174: stable-tracking/16e183d: jbt6k74.c:558: error: implicit declaration of
function 'jbt6k74_display_onoff'
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                 
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:  always         
-----------------------------+----------------------------------------------

Comment(by mrmoku):

 gitk stable-tracking..andy-tracking -- drivers/video/display

 nicely shows all commits between the two branches that touched files in
 drivers/video/display.

 for git log just put .. between the two revisions:

 git log 80f4b57fef5dcffb..9b2a35dd616a9fbe

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2174#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2174: stable-tracking/16e183d: jbt6k74.c:558: error: implicit declaration of
function 'jbt6k74_display_onoff'
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                 
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:  always         
-----------------------------+----------------------------------------------

Comment(by lindi):

 {{{
 git log 80f4b57fef5dcffb..9b2a35dd616a9fbe
 }}}
 shows 532 commits here, have there really been so many changes?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2174#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2174: stable-tracking/16e183d: jbt6k74.c:558: error: implicit declaration of
function 'jbt6k74_display_onoff'
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                 
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:  always         
-----------------------------+----------------------------------------------

Comment(by andy):

 80f4b5... was before the change to history I think, it means that it can
 have exposed the pop, rebase, push business that actually underlies the
 rebasing: maybe that's how we get 532 commits.

 Thanks for the tip about gitk mrmoku.

 I think if you can deal with the jump over to andy-tracking (it means
 taking on Balaji's regulator stuff) then it will be a lot easier going on
 since the history stuff is then working for you, there will be only a
 linear list of commits on andy-tracking to look at for changes.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2174#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2165: gtk layout differences between 2007.2 and 2008.testing
-------------------------+--------------------------------------------------
 Reporter:  iknowjoseph  |          Owner:  openmoko-devel
     Type:  defect       |         Status:  new           
 Priority:  normal       |      Milestone:                
Component:  unknown      |        Version:  unspecified   
 Severity:  normal       |       Keywords:  gtk, cacao,   
 Haspatch:  0            |      Blockedby:                
Estimated:               |    Patchreview:                
 Blocking:               |   Reproducible:                
-------------------------+--------------------------------------------------

Comment(by zecke):

 When you say Gtk+ you actually mean AWT of GNU classpath implemented with
 Gtk+? If you want someone else to even consider looking into it you should
 create a reduction. The most simple java program exposing the issue (for
 every of your issues).

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2165#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to